Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/zisofs_tools: new package
Date: Tue, 2 Jan 2018 21:58:34 +0100	[thread overview]
Message-ID: <20180102215834.2b3f83c7@windsurf.lan> (raw)
In-Reply-To: <00e4aeb9db64cb141c15a9fff0f3be4903504af6.1514923441.git.yann.morin.1998@free.fr>

Hello,

On Tue,  2 Jan 2018 21:04:11 +0100, Yann E. MORIN wrote:
> To support transparent (de)compression in iso9660, we need mkzftree,
> which comes from zisofs_tools, biundled with cdrkit.
> 
> However, cdrkit is a cmake package, but zisofs_tools is an autotools
> package, so we need a separate package just to get mkzftree, but it is
> pretty lightweight.
> 
> We just need the host variant for now,so we just add that.
> 
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

I've renamed to zisofs-tools (we more commonly use - as a separator,
and indeed your comment header in the .mk file was using this name!),
added an entry to the DEVELOPERS file, and applied. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2018-01-02 20:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02 20:04 [Buildroot] [PATCH 0/2] fs/iso9660: fix transparent (de)compression Yann E. MORIN
2018-01-02 20:04 ` [Buildroot] [PATCH 1/2] package/zisofs_tools: new package Yann E. MORIN
2018-01-02 20:58   ` Thomas Petazzoni [this message]
2018-01-02 20:04 ` [Buildroot] [PATCH 2/2] fs/iso9660: fix transparent (de)compression Yann E. MORIN
2018-01-02 20:58   ` Thomas Petazzoni

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=20180102215834.2b3f83c7@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox