Hi,
Bryan O'Sullivan さんは書きました:
Frankly, I think that the current version of the guidelines is fine. It's much better to have something not quite perfect where we can make progress than to be permanently stuck. So moving forwards with what we have suits me.
I finally took a deep look at cabal-rpm (never actually used it before!;) and realised that that is largely the source of all my problems with the current guidelines...
Below is a patch against darcs head which backports most of my changes to the guidelines to cabal-rpm. If we're using cabal-rpm for packaging then we really don't need to add rpm macros IMHO.
Thanks for all the comments.
Jens
If we're using cabal-rpm for packaging then we really don't need to add rpm macros IMHO.
I am very much in favor of having good set of base macros (under /etc/rpm/). I have developed some simple rpms using the macros posted by Yaakov and Jens (which needed to be tweaked a bit), and was quite happy with the results. I will share those in the following email.
-Rajesh
On 2008-08-28-Thu 12:23:11 am Jens Petersen wrote:
Hi,
Bryan O'Sullivan さんは書きました:
Frankly, I think that the current version of the guidelines is fine. It's much better to have something not quite perfect where we can make progress than to be permanently stuck. So moving forwards with what we have suits me.
I finally took a deep look at cabal-rpm (never actually used it before!;) and realised that that is largely the source of all my problems with the current guidelines...
Below is a patch against darcs head which backports most of my changes to the guidelines to cabal-rpm. If we're using cabal-rpm for packaging then we really don't need to add rpm macros IMHO.
Thanks for all the comments.
Jens
On Thu, Aug 28, 2008 at 3:23 AM, Jens Petersen petersen@redhat.com wrote:
Hi,
Bryan O'Sullivan さんは書きました:
Frankly, I think that the current version of the guidelines is fine. It's much better to have something not quite perfect where we can make progress than to be permanently stuck. So moving forwards with what we have suits me.
I finally took a deep look at cabal-rpm (never actually used it before!;) and realised that that is largely the source of all my problems with the current guidelines...
Below is a patch against darcs head which backports most of my changes to the guidelines to cabal-rpm. If we're using cabal-rpm for packaging then we really don't need to add rpm macros IMHO.
I want to move away from cabal-rpm actually.
The biggest pro for the macros is that we need the code to make sense to other reviewers that are not experienced with this. Any time a package needs to do something using something other than one of the macros, then we can have an expert come in an evaluate it.
Another reason for using the macros is that changes only need to be made to one place. While doing the guidelines, I had to make a number of changes to cabal-rpm, and were we not to use macros, every change to cabal-rpm would have to be backported to the packages in Fedora.
I'm going to put together some templates today.
-Yaakov
packaging@lists.fedoraproject.org