and pkg_add, don't let setup.sh start the service. The setup script is now
automatically called when not installing in batch mode.
Also, "borrow" better pkg-plist implementation from the vim5 port: it
allows to have @execs at the end of pkg-plist (thanks to O'Brien :-))
* man
A search that returns only one match will display a Location: line
instead of going directly to the result.
* shell
On Solaris, the path is not set correctly for commands entered, causing
those outside /usr/sbin:/usr/sbin not to be found.
* mysql
Clicking on a user, host, database, table or column privilege to edit
it brings up the wrong record.
For the full change log, see http://www.webmin.com/webmin/updates.html.
I also removed the WITH_UPDATES option: updates are now installed by
default. The updates filenames have a proper version and revision number,
and when a new update comes out the port should no longer break because of
sudden md5 changes.
The WEBMIN_MODULES section now fits 80 columns.
From the change log:
* The module reports the error "The PostgreSQL database on your system is
version , but Webmin only supports versions 6.5 and above". This is often
caused by the shared libraries needed by Postgres not being in Webmin's
shared library path.
See also http://www.webmin.com/webmin/updates.html for previous module
changes.
Also, a cosmetic change: be a bit more verbose when unpacking updated
modules.
PORTREVISION bump, but this will only affect people using the WITH_UPDATES
option.
The line:
for webmin_module in "${WEBMIN_MODULES}"
must be rewritten as:
for webmin_module in ${WEBMIN_MODULES}
else the port will not unpack the update tarball.
This is a very stupid bug by me. Pass the pointy hat :-(
PORTREVISION bump: people using the WITH_UPDATES option should upgrade to
this version of the port. People who do not use WITH_UPDATES and run the
stock webmin release, or update it by hand, are unaffected by this patch.
From the webmin updates page:
* Apache Webserver: if Webmin is used in non-english language mode,
"<Directory>" sections created using this module may be wrongly written
out as something like "<Directorio>".
* Squid Proxy Server: the cache_dir directive is not properly supported in
squid 2.4.
* Users and Groups: passwords for users created or modified from a batch
file are not set correctly.
(see also http://www.webmin.com/webmin/updates.html)
While I'm here, check if a webmin configuration directory already exists at
install time (post-install target): in this case, automatically run the webmin
setup script (it will insert the proper Perl paths in the webmin scripts).
Users who have multiple or different configuration directories will have to
run the script manually, as before.
PORTREVISION bump to advertise the new changes.
From the updates page:
* BIND DNS Server Reverse address records are not updated properly
if the reverse zone has a "." at the end of its name in named.conf.
Also, logging of some record additions is not done properly.
* Disk Quotas On systems using the latest Linux quotas package
(typically those with the 2.4 kernel), quotas cannot be edited or
enabled for the first time.
Submitted by: fenner's email
From the webmin updates page:
apache: Two virtual servers can be created with the same name and port. On
systems that restrict which Webmin users can edit which virtual servers,
this could be used to get around the restriction.
net: Virtual network interfaces could not be setup properly on Solaris 8.
(this should not affect FreeBSD users).
I'm removing IGNOREFILES because I cannot get a clue about which files are
updated on the webmin site. For example, if any module is updated
twice, it will be listed only once on the site's updates page.
The port will always work because the file's md5 is ignored, but I don't
know when I should bump PORTREVISION. Since the default behavior of the
port is to install the official version without updates, I prefer to have
a md5 mismatch every now and then, so that PORTREVISION can be bumped and
webmin users know when they _actually_ have to upgrade the port.
No user visible changes, so no PORTREVISION bump.
Tell the users that they must run setup.sh after every webmin upgrade:
part of the setup procedure will insert the correct perl paths in the
webmin script, and webmin will not start without these settings.
This change allows webmin to be installed/upgraded using binary packages
only. A new pkg-message file will tell the user what to do to configure
webmin for the first time. The procedure is the same after both "make
install" and "pkg_add".
Don't ${MV} /tmp/webmin.sh to ${PREFIX}/etc/rc.d: create it in ${WRKDIR}
instead, and use ${CP}.
If you move webmin.sh, you can't make install/deinstall/install: the last
install will fail because of the missing file. No user visible changes, but
speeds up testing.
When the webmin version changes on the master site, patches for previous
versions may be removed (they are not stored in a version dependent
subdirectory). This means that the port of version A will break as soon as
version B is released, because the required updates disappear.
If the updates are optional, webmin users still get a chance to install the
port without updating their ports collection. It is also easier to support
users because, by default, they will run the same "official" version of
webmin.
PORTREVISION bump: if you reinstall without WITH_UPDATES you will get an
unpatched version of webmin.
login, correct paths).
No PORTREVISION bump: if webmin has already been installed then the
postgresql module must be reconfigured by hand.
These changes are provided as perl regexes in the Makefile, because we only
want to change specific settings that could be shuffled in the next
versions of webmin (the same holds true for the postfix module).
