Kip Warner wrote:
> On Sat, 2006-05-08 at 22:51 +0100, Max Bowsher wrote:
>> Kip Warner wrote:
>>> I checked the mailing list, and unless I am mistaken, there is no
>>> uninstall target in the makefile...
>> Indeed. An 'uninstall' target is far from standard.
>>> I would like to uninstall Subversion when 1.4 moves from branch to tag
>>> officially, but I can't seem to do this? There are too many files to
>>> track manually.
>> That's a matter of opinion, but there are quite a few, yes.
>> On the other hand, searching for filenames containing 'svn' or
>> 'subversion' gets you most (all?) of them.
>>> I configured and built it myself, so it isn't as simple as using apt or
>>> Is there some script or some way of removing it?
>> Delete all the files manually.
>>> If not, this should surely be noted first in the INSTALL before
>>> people even begin to compile.
>> Why do you think so? This is hardly a matter in which Subversion is
>> exceptional. Rather, it is the common case for source installations.
> Hey Max,
> If anything, it is that last thought that is certainly a matter of
> opinion. "uninstall" is an intuitive target, just like "all" and
> "install" as well. A piece of software as complex as subversion should
> have a standard means of removal, just like any other piece of software.
> The fact that we are dealing with just the source code is hardly any
> excuse. Having no efficient way to remove it is dangerous. Moreover, I
> am not the first person to have made note of this on the mailing list.
> As for deleting all the files manually, note that you had to tell me
> that and, unlike an intuitive approach like an "uninstall" target,
> people aren't going to suspect that that was an option unless they ask
> Also, searching for svn or subversion is not mentioned in INSTALL. What
> is mentioned, however, under the heading of "Building the Latest Source
> under Unix" (but not "Building from a Tarball or RPM") is that we must
> remove libsvn, libapr, libexpat, and libneon.
We assume that people who are playing around with the source know what
they are doing, or take the time to learn. These days, most users just
grab a binary distro (whether .rpm, ..deb or .msi), all of which do
It should be fairly trivial to build, say, an RPM from SVN's source
tree, since we include RPM config scripts, too.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Aug 6 00:05:22 2006