Recipe could support multiple distroseries

Bug #516448 reported by Michael Nelson
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Undecided
Unassigned

Bug Description

Martin said:

'It seems to me from the UI, that I won't be able to easily say "build this every day in Lucid, Karmic, Jaunty and Hardy". I feel
that's the way many people are using it today'

Although we could support this in the UI by creating 4 separate recipe builds from the recipe (one for each distroseries) (and I'll updated bug 513201 with this info, as it could be a good reason for having the distroseries attribute on the build), James' notes that:

 "Should a recipe handle all distro series?!" - If we are going to do
 this then why bother building the source package on each release?
 Build the source once and then rebuild it tweaking the binary package
 version? It may be slightly more work to go from a branch that can
 build a source package for each release and a branch that can build a
 source package that can be built on each release (small difference).
 Would be a great feature to have, but I'm not sure that it's the right
 place to implement it.

Revision history for this message
James Westby (james-w) wrote :

Currently recipes are series specific, at least for the version number. In order
to build for multiple series correctly you must make sure the version numbers
are less in the older series.

We could modify the recipe format to support this somehow, but as I said
I'm not sure that it is the better solution. I think that something that works on
source packages in soyuz would be better.

Thanks,

James

Revision history for this message
Michael Nelson (michael.nelson) wrote :

Right - so it wouldn't make sense for the LP schema for a recipe to support multiple distroseries. Marking this as invalid then. So the current options to support multiple distroseries builds per recipe are:

1. Add this feature to soyuz (ie. "Build the source once and then rebuild it tweaking the binary package
 version?), or
2. An intermediate option (for which we don't need to change the schema or soyuz, but requires building each source package separately), as outlined at https://bugs.edge.launchpad.net/launchpad-code/+bug/513201/comments/4

Changed in launchpad-code:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.