All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Tim Blechmann <tim@klingt.org>
Cc: poky@yoctoproject.org
Subject: Re: deb: custom compression
Date: Wed, 7 Aug 2019 15:53:12 +0300	[thread overview]
Message-ID: <20190807125312.GA24727@localhost> (raw)
In-Reply-To: <320c4e09-e480-4a93-4ef2-a6453e4ca779@klingt.org>

On Wed, Aug 07, 2019 at 02:35:37PM +0800, Tim Blechmann wrote:
> >> poky compresses deb packages with the default flags, which these days
> >> boils down to using xz compression.
> >> trying to cut down turnaround times for local builds, i tried to modify
> >> the `package_deb` class to be able to force a low gzip compression via a
> >> `DPKG_FAST` parameter (patch attached).
> >>
> >> could this patch be accepted upstream?
> > 
> > It is specific to your problem (and sent to the wrong mailing list).
> 
> my bad (thought it's this one, as the file resides in the poky repo).
> which is the right place for it?

Not really your bad since it is complicated,
README.poky contains the details.

> > A more generic solution would be similar to OPKGBUILDCMD,
> > allowing the user to pass any parameters (including any
> > compression settings) to dpkg-deb.
> 
> something like `DPKG_OPTIONS` i'm happy to adapt the patch?

opkg (upstream defaults to gzip) has
  OPKGBUILDCMD ??= 'opkg-build -Z xz -a "${XZ_DEFAULTS}"'

For dpkg-deb I would therefore suggest
  DPKGDEBCMD ??= 'dpkg-deb'

> thanks,
> tim

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



      parent reply	other threads:[~2019-08-07 12:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07  3:28 deb: custom compression Tim Blechmann
2019-08-07  6:04 ` Adrian Bunk
2019-08-07  6:35   ` Tim Blechmann
2019-08-07 10:16     ` Alexander Kanavin
2019-08-07 12:53     ` Adrian Bunk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190807125312.GA24727@localhost \
    --to=bunk@stusta.de \
    --cc=poky@yoctoproject.org \
    --cc=tim@klingt.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.