Dne 22.7.2013 18:29, "Jóhann B. Guðmundsson" napsal(a):
As for cruft in the spec files, why not bring a proposal to the FPC to
update the packaging guidelines stating that Fedora spec files must
not contain RHEL/EPEL macros? Then the git branches would be
maintained separately and the spec files might be more easily read.
Because I have reach the conclusion that bringing anything up with FPC
is just waste of everyone's time
From their decision making ( which often to me make no sense ) to the
time it takes for them to approve and implementing changes to the
packaging guidelines ( even from "concrete" proposals ) are absurd and
more often then not takes longer time than to actually implement the
requested change on affected components which makes it impossible to
try to schedule ones free time to make those changes even scheduling
to make those changing within our development cycle.
A far more efficient approach is to adapt an ack/nack/patch approach
on the packing community mailinglist and dissolve FPC.
JBG
FYI, I already did that not a long ago:
https://lists.fedoraproject.org/pipermail/packaging/2013-March/008936.html
Vít
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
