(I am moving this to users@svn since it seems to belong there)
Um 11:14 Uhr -0600 am 2.10.2003, Hamilton Link schrieb:
>Why does the svn fink package require ruby?
Fink itself doesn't require ruby itself. But it depends on swig
during build time, because it should build the swig bindings. Whether
this fully functional right now is to be tested. That's why this
package is in the fink unstable tree.
Why is this needed? More explanation below...
>There are some other things as well that it wants to install that I
>wasn't expecting, to the tune of 40 packages or so; I was expecting
>more like a dozen, having built it by hand before (the 40 packages
>is even after I installed X11 and Octave and some other things, so
>the lowest-level stuff is already there).
Maybe i should explain how i see the goals of the fink project. In my
eyes there are three main points:
1. Coordinate the effort to port software to MacOS X
This is done by creating the package info file. You, as a user, can
look at it to see how a particular package can be compiled and
installed on MacOS X.
2. Provide an easy way to compile and install package
You can run 'fink install svn-client-ssl' and fink will do the rest
for you. This is not optimal in every situation, but (should) give
you a way of painlessly installing one of the around 3000 packages in
the fink unstable.
The packages need to be built in such a way that they include most of
the available dependencies and options, in order to make them
suitable for most users. Splitt-offs (like in the apache or
subversion case) are made after building everything. They can't be
built seperately. But see below:
3. Provide precompiled packages
Once packages are moved to the stable tree (which will not happen for
subversion before it hits 1.0) they get precompiled into .deb
packages and distributed for downloading. In the case of subversion
this will (in the future) allow you to 'apt-get install
svn-client-ssl' and in a matter of seconds you will have a svn client
installed on your MacOS X machine. This will not ask for ruby or swig
since these dependencies are only during build time.
>I'm wondering if there's a happy medium between blindly installing
>svn and the kitchen sink with fink, and installing everything
>painstakingly by hand (which in my experience is a rather exacting
>process).
>
>The apache2 module installs and subsequently archives all mpm
>modules for apache, and installs things like cyrus etc., so I can
>understand it installing more than I would have installed if I had
>downloaded the source tarballs and built it by myself, but without
>installing apache2 through fink can I still use fink to install svn?
So, to sum up and answer the two questions above, in the case of
subversion you need to build apache2 and all the depencencies of them
in order to get even only the client.
It would be great if you could do it and report back to me. Like this
it will be possible to move the svn package to the stable tree very
soon after svn hits 1.0 (or maybe beta).
I hope i answered your questions more or less,
Chris.
>thanks,
>hamilton
>
>On Saturday, February 15, 2003, at 09:20 AM, Christian Schaffner wrote:
>
>>I am in the process of producing a fink package
>>(http://fink.sf.net) for MacOS X. There is already a client
>>package: http://fink.sourceforge.net/pdb/package.php/svn-client
>>
>>Also there is apr and apr-util already:
>>http://fink.sourceforge.net/pdb/package.php/apr
>>
>>Have a look at how thing are build there...
>>
>>Chris.
>>
>>PS: Feedback is always welcome...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 2 20:42:33 2003