On Sun, 5 Aug 2001, Heikki Korpela wrote:
> As for your question: does this really mean that you can no
> longer do a pkg_add -p /opt daemontools-0.76.tgz after this
> transition? Or is /package just the default in contrast to most
> other packages that use /usr/local by default?
No, /package is more then just a substitute for /usr/local.
Here's what you get if you would install the 'new' daemontools per the
installation instructions on cr.yp.to.
It starts with the tarball. You are expected to extract it in
/package. It creates admin/daemontools-0.76. In admin/daemontools-0.76/
you run 'package/install'. You don't have an (easy) option to set the
directory where it should install the binaries.
All files will be installed in /package/admin/daemontools-0.76/ by
default. You would create symbolic links for 'programs available to users'
in /command. (and /usr/local/bin for compatibility)
I am not saying this is bad. I find it quite elegant even. My point is
that it's such a big break from our filesystem hierarchy standards that
it does not quite fit in our ports/packages system anymore...
Heck, it's a direct competitor of the ports system.
So the question remains: should we keep trying to squeeze it into our
ports system or just drop the DJB (/package) ports?
--
Cam
|