Re: [packager interface suggestion] Adding packages to buildroot directly from updates-testing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 20 Dec 2010 21:55:47 +0100
Henrik Nordström <henrik@xxxxxxxxxxxxxxxxxxx> wrote:

> fre 2010-12-17 klockan 11:22 +0100 skrev Michael Schwendt:
> 
> > +1 to some way of automating koji buildroot overrides (perhaps based
> > on FAS group membership such as provenpackagers) in order to remove
> > the releng bottleneck.
> 
> Suggestion on how to express this in the packaging process:
> BuildRequires with a version requirement pulling in from
> updates-testing if the required version can not be satisfied from the
> stable repository.
> 
> Will need some yum coding in using fallback on updates-testing or
> other selected fallback repositories on dep failures. Something I
> think is interesting for other activities as well.
> 
> This way the packager need to explicitly request the newer version in
> the spec file to have it included in the build root, and builds are
> also reproducible and self-contained with no sideband dependency
> requirements outside the spec file.

It's an interesting idea... I'm not sure if I like it thought. 

Basically it's changing spec files BuildRequires to suit our build
setup and not for 'the version this package needs to build'. 

So, folks who take our src.rpms to rebuild/build elsewhere will find
this anoying. Also, there's not any easy way to see what the real
version is... 

# We need libfoo-1.0 or better, but 1.2-5 is the latest in
# updates-testing we want to build against: 
BuildRequires: libfoo-1.2-5

I'd like to propose a different plan: 

* Write up a wiki page/howto/sop for when and how to do overrides (I
  think we might already have one). 
* Allow packagers to do overrides. 
* Have a daily cron job that mails out: 
1. An email to whoever tagged the build into override. 
2. a full list to devel list? rel-eng list? 

This way you can add your override and use it to build what you want,
but you will be nagged every day to check and remove the override if
you no longer need it. If you drop your emails or otherwise don't
notice it, rel-eng or other folks on the devel list could ask you why
you still have the override in place. 

Thoughts?

kevin

Attachment: signature.asc
Description: PGP signature

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux