From owner-freebsd-ports  Tue Aug 27 14:59:33 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA03512
          for ports-outgoing; Tue, 27 Aug 1996 14:59:33 -0700 (PDT)
Received: from netcom2.netcom.com (kientzle@netcom2.netcom.com [192.100.81.108])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA03507
          for <freebsd-ports@freebsd.org>; Tue, 27 Aug 1996 14:59:26 -0700 (PDT)
From: kientzle@netcom.com
Received: (from kientzle@localhost) by netcom2.netcom.com (8.6.13/Netcom)
	id OAA22646; Tue, 27 Aug 1996 14:59:23 -0700
Message-Id: <199608272159.OAA22646@netcom2.netcom.com>
Subject: Re: Linux async vs. FreeBSD sync (fwd)
To: freebsd-ports@freebsd.org
Date: Tue, 27 Aug 1996 14:59:23 -0700 (PDT)
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

An alternative package system that I've been using successfully for several
months now is to install _every_ application in it's own private directory,
and then populate /usr/local/{lib,bin,include,man} with appropriate
symlinks.  For example, I have "ispell" installed in /usr/local/app/ispell
as follows:

/usr/local/app/ispell/bin - public executables
/usr/local/app/ispell/lib - public lib file
/usr/local/app/ispell/man/man? - Man pages

I've then cobbled a quick Perl script that destroys and then
re-builds the following directories:

/usr/local/man/man? - links to /usr/local/app/*/man/man?/*
/usr/local/lib - links to /usr/local/app/*/lib/*
/usr/local/include - links to /usr/local/app/*/include/*
/usr/local/links/bin - links to /usr/local/app/*/bin/*

(I chose /usr/local/links/bin rather than /usr/local/bin to avoid
some transition headaches.)

The big advantage of this scheme over the current FreeBSD package
scheme is that it's very easy to add a new port to this system,
since you don't have to track down every file and enter it into
some database.  Similarly, removing packages is equally simple: just
delete the package directory and rebuild the link directories.

Currently, this doesn't handle package dependencies, and has some other
weaknesses, but I think it has serious advantages over the current system.
In particular, it easily handles new programs and ports as well as
existing packages.

If anyone's interested, write me directly, as I don't subscribe.

                                - Tim Kientzle
                                kientzle@netcom.com


Forwarded message:
> From joerg_wunsch@uriah.heep.sax.de Tue Aug 27 14:42:11 PDT 1996
> Article: 28726 of comp.unix.bsd.freebsd.misc
> Newsgroups: comp.unix.bsd.freebsd.misc
> Subject: Re: Linux async vs. FreeBSD sync
> Date: 25 Aug 1996 13:37:03 GMT
> 
> celestra@ix.netcom.com (Arthur D. Jerijian) wrote:
> 
> > I do have a wish list for FreeBSD, however.  A packaging system similar
> > to Red Hat Linux's RPM or Debian's dpkg would be nice. ...
> 
> Things of this kind are perhaps best discussed on the mailing list
> freebsd-ports@freebsd.org.  Even if you are not subscribed, write
> there.  Too many contributors won't notice your opinion here in
> Usenet.  (Remember, *BSD development and support _mainly_ happens on
> mailing lists.)
> 
> -- 
> cheers, J"org
> 
> joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
> Never trust an operating system you don't have sources for. ;-)