python version grabbing
by seth vidal
Hey,
Do you think it'd be worth it to have a section on getting the python
version for site-packages for rpm building? Maybe with the standard
routines?
-sv
19 years, 1 month
- 4
- 3
Template .spec file for conventions?
by Scott Lawrence
It looks as though there's a consensus developed around how packages
should be named. Being fairly new to rpm building, I have not
understood all the details of the discussions around how best to
implement those conventions. Might it be possible for one of you who
does understand it to supplement the naming guidelines with a
skeleton .spec file that illustrates how to do it, along with whatever
is required of the surrounding build system?
--
Scott Lawrence
Consulting Engineer
Pingtel Corp.
http://www.pingtel.com/
+1.781.938.5306 x162
19 years, 1 month
- 4
- 3
PackageNamingGuidelines comments
by Elliot Lee
Hi guys, I'm late to the party, but overall it looks good.
The stuff that could improve is eliminating "non-numeric version in
release". For the sake of keeping things sane and simple, the Version:
should normally match the upstream version. If there are versions such as
0.1beta that compare as "greater than" 0.1, then epoch should be used.
That's one of the situations that epoch was created for. Making rules
about munging version & release in the general case, for the sake of
avoiding epoch in the special case, just complicates things unnecessarily.
Inter-repo wars are going to exist whether or not Fedora chooses to use
epoch - they have no bearing on this decision.
Cheers,
-- Elliot
19 years, 1 month
- 9
- 17