On Thu, 24 Feb 2005, Panu Matilainen wrote:
Feedback is welcome, and encouraged.
Looks good, I would propose a standard SPEC file (in the SRPM) formatted as:
%{name}-%{version}-%{release}-%{repotag}.spec
If your working on a SPEC file and install several other versions, this would prevent SPEC files replacing others. And the origin is clear too.
Eek, please lets don't. That's what CVS and distro brances of packages are for.
How does that affect SPEC files in SRPMs ? Afaik FE (and RH) SRPMs have a %{name}.spec files inside the SRPM which are not distinguishable. Even when FE or RH is using CVS and distro branches.
I'm talking about renaming the SPEC file to something more identifiable as %{name}.spec before creating the SRPM. Nothing else. DAR is doing this as part of the pre-processing stage of the SPEC file.
I just don't think that renaming spec to some awfully long name buys you any safety at all and only looks ugly as hell :) The SRPM can contain other bits (patches, sources) which overwrite one another when working with several versions of the package in a "normal" rpm build tree.
- Panu -
