According to Hamish Moffatt:
> On Wed, Jul 14, 1999 at 05:32:32PM -0700, Gary Kline wrote:
> > On Thu, Jul 15, 1999 at 10:10:23AM +1000, Hamish Moffatt wrote:
> > > I envisage a /compat/debian tree, which would be like / to linux.
> > > Ie /compat/debian/usr/bin, /compat/debian/usr/share/doc etc.
> > >
> > > However, I don't know if FreeBSD will let us do this. Although we could
> > > easily move /usr/bin to /compat/debian/usr/bin, this would not work for
> > > /usr/lib and /usr/share, whose paths are probably hardcoded into binaries.
> > > Ideally, the kernel would search /compat/debian for the stuff first
> > > (or /compat/linux). I don't know if it does, though -- /compat/linux might
> > > be intended only for system libraries (libc, libm, etc) and not for
> > > binaries.
> >
> > Could we build these by-hand and have the configuration|build
> > script look for our DebianBSD (linux) binaries in /some-
> > /compat/debian/library/path? Then every BSD binary would work
> > and so would all the Debian user-side tools.
>
> The idea was to avoid rebuilding any packages, though.
>
>
It's time to ask some questions about the Linux packages
suite. Does dpkg allow the user to install the src code
in some /usr directory; then build and install the binary
after it's been built? ...Or does dpkg just install the
binary (and any ancillary files?
I very rarely just install a binary; I prefer building
from source.
I understand that any pre-built Linux//Debian binaries
could pretty easily just-drop-in to /compat/debian/*;
which is fine. But for hackers who *prefer* to build
from scratch, ... (?)
Sorry if I'm not in-sync here.
gary
>
>
--
Gary D. Kline [EMAIL PROTECTED] Public service Unix
