On 2006-08-17T21:41:52, Lars Marowsky-Bree <[EMAIL PROTECTED]> wrote:
Oh, one more footnote to myself:
My specfile is geared towards building from CVS.
Something which Alan takes an issue with, and probably rightly so, but
because the process to generate the tarball already generates some of
the target files depending on the outcome of configure, and as evidenced
by the specfile generation then no longer is entirely portable, I'd have
to rerun autoconf + automake et cetera _anyway_ to make sure that I
build a clean package, I didn't see the point of first building a dist
tarball and then throwing it into the build system.
Ultimately, I'd like the specfile to be capable of building _either_
with a tarball generated by make dist, or a tarball generated from
taring up an arbitrary checkout from CVS/mercurial.
I don't think there's actually anything in my specfile which stops this
- it should work with both -, but I thought I'd raise that point
explicitly so you're aware of it.
Thanks,
Lars
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
