David Summers wrote:
>I guess we could take out the REQUIREMENT for /sbin/install-info and could
>test for that program before trying to run it.
>
Best way to do.
>Another possibility would be an RPM for SUSE that installs that
>package or file. Or is that functionality present on SUSE but in a
>different place?
>
What is install-info used for (as I am running SuSE I never "met" this
program)
>
>Another possibility would be to just whip up your own /sbin/install-info,
>but that would probably not be a good requirement for binary
>installations.
>
Sounds like this might work on some EPM based distributions but break on
others.
>
>Anybody see any other (better) options or possibilities?
>
>At this point I'm leaning towards taking out the requirement from the SPEC
>file and testing for the existance of the /sbin/install-info program and
>running it if it is found.
>
+1
>
>
>Thanks for the feedback! I've only had a total of about 3 people in the
>last 9 months provide feedback to me.
>
> - David Summers
>
Guess, most of the people fiddling with subversion take the latest code
(pulled out of the repos)
and build their stuff. There seemed to be an attitude to the RPMs like:
"oh well, we have it, this is great.
but anyhow, we wont use them. its just great cause as soon as other
people (non developpers) will
start using subversion we have them."
My motiviation for using the RPM is: I want to develop an app that is
not embedded into the svn core.
So I am more of a user of the API. And as soon as I want people to try
my stuff they will ask for the
RPMs....
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 18 18:40:20 2002