-upstart subpackage vs tranditional initscripts

Chen Lei supercyper1 at gmail.com
Fri Jun 4 03:16:00 UTC 2010

2010/6/4 Kevin Kofler <kevin.kofler at chello.at>:
> The problem is that the mandatory functionality (SysV-style initscripts
> compliant to our guidelines) gets pushed to a subpackage to make room for
> the optional and completely unneccessary junk, and that in some cases yum
> prefers the nonstandard subpackages.
> Plus, he's also violating other guidelines, e.g. for this package:
> http://koji.fedoraproject.org/koji/buildinfo?buildID=176308
> Version contains a SVN revision tag which MUST be in Release instead
> according to our guidelines. (Thanks to Chen Lei for pointing that out.)
> (And look at the mess that nonstandard versioning made to the bumping tool
> spot used, see the insane Release values it produced. We have versioning
> rules for a reason.)
>        Kevin Kofler
> --
I found that spot disable building static libs in his package two days
ago, but he reenable yesterday, I really don't know why.

Chen Lei

More information about the devel mailing list