2001-01-03 11:55 knu
* README.knu, cvsweb.cgi: Don't forget to add $query to the URL
when redirecting. Now module alias redirection and Attic
redirection work with all sticky variables preserved. (Previously
they didn't work against a non-default cvsroot)
Put a text field on each directory view that allows user to jump
directly to an arbitrary module, which can be specified either by a
full module/file path or by a module alias.
2001-01-03 08:34 knu
* README.knu, cvsweb.cgi, cvsweb.conf: List CVS repository entries
in the specified order, not alphabetical.
Now /usr/local/etc/cvsweb/ is the default directory for
configuration files.
o Really install its tiny search scripts
o Build package with or without apache installed (hacky hacky)
o Fix pkg-message, tell users to copy bk2site *.gif and *.pl manually
when build without apache or install via package
o Hide perlre in post-patch target, which looks like "Panic ! Help !"
o Remove patch file. (Now handled simply by perlre)
o Shorten pkg-comment (portlint doesn't like the longer one)
o Bump PORTREVISION
For systems with apache installed, now it's
ready-to-run-without-manually-doing-anything.
prune unfetchable master site.
NOTE: there are two(or more) nethack-3.2.2.tar.gz that have different
content on the earth. The one at jnethack.org has some fix but it is
available only there. Be careful if you are willing to add new master
sites.
PR: 20564
Submitted by: Jimmy Olgeni <olgeni@uli.it>
mkpbuild just builds a port with WRKDIRPREFIX and PREFIX set to a
directory in /tmp, and with the owner and group variables set to the
user. A placeholder - in future, it'll have build error/log parsing.
mkpinstall's claim to fame is to do the same, except with "make install"
instead of "make build", and it then parses the mtree file, and compares
that and the current directory tree and the files, and auto-generates a
plist.
They're not pretty, but they finish the mkptools set basic
functionality: automatic skeleton generation with mkpskel, on-extraction
requirements guessing, and plist generation.
Future direction might be parsing build and install failures, checking
for '/usr/local' abuse, more requirements guessing, and stuff like that.
