pseudo-flavour, it affects the -main package by building with pthread
(we don't want that by default, it affects e.g. svn diff | less).
- roll various PFRAG.shared-foo for the subpackages into PLIST-foo
- add a comment noting that autoconf should be 2.63
- bump PKGNAMEs
ok stsp (maintainer).
Also:
* Native make now works fine so don't use gmake.
* Disable storing of plaintext passwords for all servers in the system-wide
'servers' config file, instead of disabling storage of all kinds of
passwords in the system-wide 'config' config file.
The new store-plaintext-passwords=no option, which has existed since 1.6.0,
overrides a yes/no prompt which subversion now usually presents before
storing passwords in plaintext. gnome-keyring stores passwords encrypted.
* Update the main DESCR to reflect current reality.
* Add a patch which fixes a broken regression test in the ruby bindings
which accidentally slipped into 1.6.5 release.
* Put the gnome-keyring subpackage into REGRESS_DEPENDS to make
auth-test pass (it loads DSOs at runtime and can't find them if
the gnome-keyring subpackage isn't installed).
Tested on i386 by me and alek@, on i386/amd64 by steven@,
and on sparc64 by Edd Barrett.
ok steven@
also,
- add various utilities from contrib/ and tools/
- update svn2cl to version 0.11 (has a fix for OpenBSD ksh)
- install SVN::Fs man page
from maintainer Stefan Sperling, tweaked a bit by me
the doco claims this is safe cos the directory has extremely restricted
permissions, but noone i know agrees with this or feels safe. this change
installs a config under /etc/subversion/config that disables this
behaviour.
discussed with pval@ ckuethe@ ok robert@ sturm@ ajacoutot@
the FULLPKGPATH, thus providing changes to packing-lists which shouldn't
happen, and making update more difficult.
Accordingly, bump all pkgnames with PSEUDO_FLAVORS, and provide an
update @pkgpath for the bug for most of them (left out the ones with 3
or 4 pseudo flavors for space constraints...)
Subversion is a free/open-source version control system. That is,
Subversion manages files and directories over time. A tree of files
is placed into a central repository. The repository is much like an
ordinary file server, except that it remembers every change ever made
to your files and directories. This allows you to recover older versions
of your data, or examine the history of how your data changed.
In this regard, many people think of a version control system as a
sort of time machine.
Joint work with msf@, Sigfred H?versen, Alex Holst and Steven Mestdagh
ok naddy@, go ahead msf@
