--On Saturday, December 10, 2005 4:05 PM -0600 David Summers
<david@summersoft.fay.ar.us> wrote:
> I'm all for making things better. I'm not sure why "Building from a
> checkout implies that you're building from a repo version, not from a
> 'release'". For instance, when I build my final RPMs for a release I
> checkout from the tag and build. I know it is *different* than most
> people are used to, I just haven't seen that it makes a big difference.
> Maybe it does. Most of the time when a packager builds an RPM they are
> not building directly out of the source control, they have a "release"
> tarball that they build from. In that situation I would agree with you.
> However, since I'm building directly out of the soure control, it sure
> makes it nice to do it this way from my point of view.
Ok, I agree, and so does the RPM maintainer:
<https://lists.dulug.duke.edu/pipermail/rpm-devel/2005-December/000630.html>
Note that he has a couple of questions about Subversion (and CVS)
integration into RPM in that post.
> I suppose I could run the "dist.sh" procedure during the RPM generation
> sequence but I don't like that becuase it requires downloading the latest
> neon, apr, apr-util, etc, which I'm just throwing away during my RPM
> build anyway because I am relying on the already installed versions
> instead of the "latest" at the time of the build. On platforms with
> existing neon, apr, apr-util, bdb, etc., it is important to use the
> platform installed versions, otherwise we get into a big mess with trying
> to have shoe-horn in new depedencies with software which already has
> existing dependencies. I hope I said that all correctly. Anyway, I've
> tried running different BDB and APR/APR-UTIL with stuff before. It can
> be done but is a big headache so far. Maybe I'm doing something wrong.
No, that makes sense, esp. when working from a tagged check out. One just
has to accept that the tarball is "less pristine" than the upstream tag
from which it's generated, and will produce a different result. Ideally the
RPM-based distro will pull a copy directly from the "vendor" (Subversion
project) repository into its own repo (which I believe is CVS for Red Hat)
and then RPM builds from that. The copy in the distro's repo is logically
equivalent to a tarball for other packages. Only the delivery system (svn
export versus a tarball copy) is different.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 13 07:18:22 2005