|
Home > Archive > Debian Developers > August 2005 > Additional binary package generated by a source package: how to handle this ?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Additional binary package generated by a source package: how to handle this ?
|
|
| Xavier Roche 2005-08-28, 5:51 pm |
| Hi folks,
If a source package "foo", which produces a binary package (say, "bar"), also produces an additional "baz" package in an updated version, how this should be handled ? Any specific things to do, apart from appending the debian/control file (and debian/baz.
files) with the new entry ? Will the autobuilders handle this without troubles ?
Cheers,
Xavier
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Wouter Verhelst 2005-08-28, 8:49 pm |
| On Sun, Aug 28, 2005 at 11:07:24PM +0200, Xavier Roche wrote:
> Hi folks,
>
> If a source package "foo", which produces a binary package (say,
> "bar"), also produces an additional "baz" package in an updated
> version, how this should be handled ? Any specific things to do, apart
> from appending the debian/control file (and debian/baz.files) with the
> new entry ?
No.
> Will the autobuilders handle this without troubles ?
Yes.
You will have to go through NEW processing again, though.
--
The amount of time between slipping on the peel and landing on the
pavement is precisely one bananosecond
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|