the use of build-ids for .ddebs and add refcounting support
> (like has been done for multiarch AFAIK) to dpkg for them, so we don't need to
> worry about Conflicts / Replaces.
--
.''`.
: :' : “You would need to ask a lawyer if you don't know
`. `&
On 26/03/11 09:10, Raphael Hertzog wrote:
> On Sat, 26 Mar 2011, Emilio Pozuelo Monfort wrote:
>> I'd also mandate the use of build-ids for .ddebs and add refcounting support
>> (like has been done for multiarch AFAIK) to dpkg for them, so we don't need
>> to
>
On Sat, 26 Mar 2011, Emilio Pozuelo Monfort wrote:
> I'd also mandate the use of build-ids for .ddebs and add refcounting support
> (like has been done for multiarch AFAIK) to dpkg for them, so we don't need to
> worry about Conflicts / Replaces.
For multi-arch, it's the
package doesn't exist in the archive).
>
> To simplify the archive processes i would prefer having a ddeb per
> binary package instead of source package. It must have the name
> $binary-ddeb and must have the same version as $binary. The ddebs will
> get separate Packages files s
ve processes i would prefer having a ddeb per
binary package instead of source package. It must have the name
$binary-ddeb and must have the same version as $binary. The ddebs will
get separate Packages files similar to the udebs. It is even easier
for our users that they don't need to find out
On 25/03/11 23:13, Philipp Kern wrote:
> Are there dependencies from the -ddeb to the binary? Because you'd want to
> update/upgrade your ddeb when you update the library, otherwise it becomes
> useless. I imagine there can't be given that the binaries of our source
> package might not be co-inst
On 2011-03-25, Emilio Pozuelo Monfort wrote:
> On 25/03/11 22:24, Torsten Werner wrote:
>> On Fri, Mar 25, 2011 at 10:54 PM, Emilio Pozuelo Monfort
>> wrote:
>>> http://people.debian.org/~pochu/debhelper_8.1.2+nmu1_all.deb
>> Thanks. The name of the ddeb for gzip is gzip-ddeb. Can we rely on
>> t
On 25/03/11 22:24, Torsten Werner wrote:
> On Fri, Mar 25, 2011 at 10:54 PM, Emilio Pozuelo Monfort
> wrote:
>> http://people.debian.org/~pochu/debhelper_8.1.2+nmu1_all.deb
>
> Thanks. The name of the ddeb for gzip is gzip-ddeb. Can we rely on
> that schema or is there another way to find the nam
On Fri, Mar 25, 2011 at 10:54 PM, Emilio Pozuelo Monfort
wrote:
> http://people.debian.org/~pochu/debhelper_8.1.2+nmu1_all.deb
Thanks. The name of the ddeb for gzip is gzip-ddeb. Can we rely on
that schema or is there another way to find the name of a deb package
from its ddeb package? Rationale:
On 25/03/11 21:46, Torsten Werner wrote:
> Thanks for the explaination.
>
> On Fri, Mar 25, 2011 at 10:38 PM, Emilio Pozuelo Monfort
> wrote:
>> Apply the attached patch to debhelper (applies cleanly on debhelper 8.1.2).
>
> May I download a pre-built debhelper from somewhere?
http://people.deb
Thanks for the explaination.
On Fri, Mar 25, 2011 at 10:38 PM, Emilio Pozuelo Monfort
wrote:
> Apply the attached patch to debhelper (applies cleanly on debhelper 8.1.2).
May I download a pre-built debhelper from somewhere?
Thanks,
Torsten
--
To UNSUBSCRIBE, email to debian-devel-requ...@lis
On 25/03/11 18:22, Torsten Werner wrote:
> are there any example packages that build ddebs? That we can use for
> testing dak?
It should happen automatically if you patch debhelper (and CDBS to automatically
get .ddebs out of CDBS-using packages) with my patches. I have just refres
Hi Josselin,
Am -10.01.-28163 20:59, schrieb Josselin Mouette:
> Would it be possible to add support for ddebs?
are there any example packages that build ddebs? That we can use for
testing dak?
Cheers,
Torsten
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subj
13 matches
Mail list logo
