[392] in SIPB_Linux_Development

home help back first fref pref prev next nref lref last post

Re: Package Lists

daemon@ATHENA.MIT.EDU (svalente@MIT.EDU)
Fri Feb 4 20:03:48 1994

From: svalente@MIT.EDU
Date: Fri, 4 Feb 94 20:03:30 -0500
To: warlord@MIT.EDU
Cc: linux-dev@MIT.EDU
In-Reply-To: Derek Atkins's message of Fri, 04 Feb 94 15:05:18 EST <9402042005.AA26518@toxicwaste.media.mit.edu>


> I put the package lists under RCS.  This way we can know who was
> playing with what.

That doesn't seem necessary, but, fine.

> I have also recreated all the packages (well, I am about to do that as
> soon as I send this message).

Fine.

> The old packages will be under package.tgz.bak.

Don't bother.  Nuke 'em.

> A very frustrated
> -derek
> (PS: I'm frustrated because this is the third package in the last couple
> days that I found out-of-date)

Sigh.  The Story(tm):

I created the package lists back when we were still running SLS and
had no organized source tree by doing "ls -1R /usr/athena" and putting
each file it listed in a package that sounded right.  Needless to say,
I guessed wrong on a lot of the stuff I had never used, but I went
ahead and made the packages anyway, because Resnet was ready before I
was.  (And my email messages asking others to check the package lists
were basically ignored.)

Now that I feel I have some time before the next wave of people comes
looking for the packages, I'm reorganizing each package one by one, my
doing "make install" in the source trees and seeing what truly goes
where.  I haven't been announcing the changes because they're not
done.  I haven't been remaking the packages because I don't expect
many people to be installing them anytime soon.  So it's my fault that
many package lists are newer than the packages, and it's somewhat
intentional.  Don't get so worked up over it.

Here are some changes I want to make at some point...

- Make sure each package is correct and complete.

- Make the packages Slackware packages (and distribute "pkgtool" for
  those who aren't running Slackware.)  This will keep records of what
  was installed (yay), and will allow us to create an installation
  script that gets automatically run when the package is untarred (for
  example, the kerberos install script will fix /etc/services.)  This
  will be very useful.

- Split up mh into mh-base and mh-extra.
- Split up "lib" into krb-lib, zephyr-lib, motif-lib, etc.

There are lots of others that are not coming to mind right now.

Have a nice day.
-Sal.

home help back first fref pref prev next nref lref last post