Le dimanche 07 juin 2009 à 12:31 +0300, Panu Matilainen a écrit : > Btw your initial suggestion of collecting the common stuff into macros > and converting packages to use them would be useful on several ways: > a) Finding out the things that *are* common among lots of packages. While > numerous cases are well and widely known already, I suspect there might > be some that are only specific groups know about (possibly eg java > related packages, I dunno). > b) Making the usages of the common patterns easy to spot by grepping. > c) The transition period cruft can be hidden inside the common macros > without polluting every spec with it. Won't work IMHO. One characteristic of pre-macroized specs is that their authors have found lots of "interesting" ways to do about the same thing with different instructions (usually missing some problems). If you don't want this old processing to collide and interfere with your new shiny processing you need the call to the new processing to be explicit, so packagers can check for problems before enabling it. -- Nicolas Mailhot
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
