From: Alexander Hoogerhuis <alexh@ihatent.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RPM build target fixes
Date: 10 Mar 2002 18:17:50 +0100 [thread overview]
Message-ID: <m37kok8hq9.fsf@lapper.ihatent.com> (raw)
In-Reply-To: <E16k2v8-0006QY-00@the-village.bc.nu>
In-Reply-To: <E16k2v8-0006QY-00@the-village.bc.nu>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > > Thats exactly the opposite of what is expected
> >
> > How so? Given that it actually cleans up after itself you are not left
> > with multiple .spec files in any directory? Or have I missed something?
>
> Most source rpm packages come with a [packagename.spec] file without a
> version.
>
OK, so the .spec in the tarball should be without (for rpm -ta), and
the one left in %_topdir/SPECS should carry it?
Basically why I made the .spec files carry the version was that I have
several trees (linux-2.4-[ac|plain|clean|mystuff] and
linux-2.5-[dj|plain|clean]) and that way I can build the trees without
interfering with eachoter, as all the .spec files, tarballs, RPMs and
SRPMs will actually be named something like
kernel-$version-$extraversion. That way, if you build two trees they
wont stamp on eachother.
ttfn,
A
--
Alexander Hoogerhuis | alexh@ihatent.com
CCNP - CCDP - MCNE - CCSE | +47 908 21 485
"You have zero privacy anyway. Get over it." --Scott McNealy
prev parent reply other threads:[~2002-03-10 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-09 21:03 [PATCH] RPM build target fixes Alexander Hoogerhuis
2002-03-09 21:35 ` Alan Cox
2002-03-10 9:31 ` Alexander Hoogerhuis
2002-03-10 12:59 ` Alan Cox
2002-03-10 17:17 ` Alexander Hoogerhuis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m37kok8hq9.fsf@lapper.ihatent.com \
--to=alexh@ihatent.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox