PLISTs.
Note: I know that this is going to break some symlinks and/or .so
includes, I will back some of these out as I run into these during
package building.
all the COMMENTs! No package names, no version numbers, no "this is
absolutix-3.1.2" type comments that have zero information contents.
Now, without any bad examples to follow, nobody has an excuse to import
a port with those kind of comments. :)
Phew! 238 ports modified!
a scan file if supscan is run on that collection.
Supfilesrv will not blindly take scan to be the scan file for any release
that does not specify a scan file. It will take it if there is no releases
file (there can only be on collection in that case).
Supscan now takes optional "-r release" args to specify scanning only certain
releases in a collection.
1) Preserve the timestamp of an updated file even if a command that is
executed because of the update modifies the file. This allows you to
do things like export /etc/hosts and when it changes, customize it based
on the target host with a simple script, but not upgrade it every time
sup is run.
2) Add the "unlinkbusy" SUP option. The goal of this option is to allow
you to upgrade binaries and libraries on a running system via sup
automagically just like "install" does.
3) Add the "rename" collection function. This allows you to store a file
on the server under one name, but have it land on the client under another.
All of these changes are targeted toward making SUP a better administrative
tool. A reverse rdist if you like. TCS uses sup to keep over 100 HP
workstations in sync with a master machine and performs all maintainence
including new software installations and system patches using it without
a hitch. Of course, the SUP collections are fairly complicated
(HUP inetd when inetd.conf changes is a very simple example), but it
definitely works and works well.
This patch also includes full support for the HPUX platform. I didn't
see any reason to strip it out since HPUX was the target platform of
the original work and it may be of use to other people.
2.0-current distinguishes between crypt() and cipher() technology and
in this case, the crypt() call was for password authentication on the
file server. If building an encrypting sup, link with -lcipher -lcrypt,
if building a normal sup, link with -lcrypt.
since it should have been in net/. Since not too many people are grabbing
ports yet I'm going to be nasty and relocate it in the repository.
Submitted by: jkh
