My personal policy is that everything that goes under /usr /bin /sbin etc. 
should by installed by the OS package manager, while direct installation (“make 
install”) under /opt is fine, provided that a non privileged user account is 
used.

So I would suggest to create a system user account (say owfscode) which is the 
owner of the install tree (by default /opt/owfs) and follow the normal clone, 
bootstrap, configure, make, install, sequence, under user account owfscode.

More explicitly, run
as root:

# adduser --system owfscode
# mkdir /opt/owfs /opt/owfs-build
# chown owfscode /opt/owfs /opt/owfs-build

as owfscode:

$ git clone git://git.code.sf.net/p/owfs/code /opt/owfs-build
$ cd /opt/owfs-build
$ ./bootstrap
$ ./configure --disable-owperl --disable-owphp --disable-owpython 
--disable-owtcl --with-systemdsystemunitdir=no
$ make
$ make install

Perl, php, tcl, and python have to be disabled, because the default Makefile's 
insist in installing them system wide (under /) instead of under the install 
prefix /opt/owfs. If you need them it is pretty simple to install them 
manually. (And of course, if you use python you should use virtualenv+pip, not 
clutter the system wide python.)

Same holds for systemd, which actually I do not use. (So I cannot give advice 
on how systemd should be configured if one choses to install OWFS systemd unit 
files under /opt/owfs/lib/systemd)

With this installation procedure everything is confined under /opt/owfs so I do 
not see a real benefit in building .deb packages: of course you have to adapt 
PATH, MANPATH, etc.

Stefano

> On 28 Dec 2015, at 23:19, Markus Gaugusch <mar...@gaugusch.at> wrote:
> 
> Hi,
> 
> I'm using Ubuntu 15.10 and the included owfs (2.9p8) is quite old. I'd 
> like to build a current version, but all information I could find for 
> building on Ubuntu is quite outdated (based on 12.04 and cvs).
> 
> Best option for me would be to build .deb packages. I switched to Ubuntu 
> recently and I'm not yet used to building of deb packages. Can anybody 
> help me? :-)
> (In former times I built RPM packages using an adapted spec file).
> 
> thanks!
> Markus
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers


------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to