Re: Copy packages to same PPA, different distro

["Celso Providelo" <celso.providelo@xxxxxxxxx>]

On Mon, May 26, 2008 at 8:50 PM, Dan <danmbox@xxxxxxxxx> wrote:
> Hi,
>
>> {{{
>> | | Copy binaries
>>
>> Whether or not to copy the binary packages for the selected sources.
>> }}}
>
> But "Copy Binaries" doesn't give me any assurance that the binaries
> will actually be installable in the target distro. How do I check
> that? Could Launchpad do a check?

Launchpad checks if the binary version is 'publishable' anything else
can't be accurately checked, unfortunately.

Note that 'installable' and 'fully-functional' are also different concepts.

>>> What I used to do is build on Gutsy, then copy source to Hardy. Soyuz then
>>> built the Hardy version of those packages but they were never made
>>> available
>>> to users.
>>
>> Right, but that shouldn't and will not be allowed anymore, see the example:
>
> Yes, it doesn't work because the naming convention doesn't support it.
> Is it possible to come up with a different naming convention that
> avoids this conflict? I.e. can the .deb's for different distributions
> either have different names, or be placed in different directories? Is
> the "/pool/..." structure the only way to do it? IIRC there is a
> different type of Debian repositories (trivial vs. automatic)

It's not only about the archive topology, but mainly for packaging consistency.

If foo-bin works fine for gutsy and hardy why would you have to
rebuild it and in case it doesn't work as expected in a later series
the issue should be fixed and documented as a new version of the
package. So the evolution goes on, step by step.

>> Maybe, but I'm not sure how valuable it would be. Do you have any
>> specific use-case in mind ?
>
> I'm not sure what Pau meant by "automating" either.
>
> What I can say is that I'd like to be able to upload a source package
> and have it build for all distributions (or at least the recent ones,
> e.g. Hardy + Gutsy). I'm not sure if it's feasible, but it would be
> great.

See above.


-- 
Celso Providelo <celso.providelo@xxxxxxxxxxxxx>
IRC: cprov, Jabber: cprov@xxxxxxxxxx, Skype: cprovidelo
1024D/681B6469 C858 2652 1A6E F6A6 037B B3F7 9FF2 583E 681B 6469