On Mon, 10 Oct 2011 17:18:10 -0400
Bill Nottingham wrote:
Rahul Sundaram (metherid(a)gmail.com) said:
> On 10/10/2011 08:52 PM, Thomas Spura wrote:
>
> > So there doesn't need to be more co-maintainers (which is welcomed
> > anyway), but it would help to get such updates pushed to stable
> > directly like it was without the forced period in updates-testing
> > or a heads up before doing such an update.
>
> I think the heads up should be automated via the build system.
If the required updates are due to version checks in the extensions,
it might be possible to have RPM have a dependency generator that
checks these and outputs the appropriate Requires/Conflicts lines,
such that this could be easily caught by AutoQA.
Implemented and proposed as a subpackage to mozilla-filesystem at:
https://bugzilla.redhat.com/show_bug.cgi?id=745038
Any extension, which BR: mozilla-build then has the correct requires,
if it's installed correctly.
"Correctly" means here, without symlinks, like I currently do in
noscript and other extensions are doing it too right now.
I'd propose to finally have mozilla-noscript, which pulls all
subpackages, e.g. firefox-noscript and seahorse-noscript etc, and only
those subpackages require firefox OR seahorse.
Comments?
-Tom