From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] mtd-utils: Version bump of the GIT source
Date: Thu, 2 Apr 2009 11:40:33 +1100 [thread overview]
Message-ID: <20090402004033.GC29488@cloud.net.au> (raw)
In-Reply-To: <1238098807-5648-5-git-send-email-mroth@nessie.de>
On Thu, Mar 26, 2009 at 09:20:06PM +0100, Michael Roth wrote:
> GIT version of mtd-utils bumped to 2009-03-26 and support
> for the included mkfs.ubifs added.
>
[...]
> +config BR2_PACKAGE_MTD_MKFSUBIFS
> + bool "mkfs.ubifs"
It's pretty unlikely that you would want mkfs.ubifs on your target
system but I guess it's correct to include it. Actually I may need it
for my current project anyway :-|
> + default n
That's superflous.
> + depends on BR2_PACKAGE_MTD_UTILS_GIT && BR2_LARGEFILE && BR2_PACKAGE_E2FSPROGS
Depending on BR2_PACKAGE_E2FSPROGS also means a bunch of other binaries
get included by default. I think libuuid needs to be split out into a
separate package built from the same source tarball.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2009-04-02 0:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 20:20 [Buildroot] [PATCH 0/5] mtd-utils Michael Roth
2009-03-26 20:20 ` [Buildroot] [PATCH 1/5] mtd-utils: Prepare for version dump Michael Roth
2009-03-26 20:20 ` [Buildroot] [PATCH 3/5] mtd-utils: Prepare for upcoming mtd-utils with included mkfs.ubifs Michael Roth
2009-03-26 20:20 ` [Buildroot] [PATCH 4/5] mtd-utils: Version bump of the GIT source Michael Roth
2009-04-02 0:40 ` Hamish Moffatt [this message]
2009-03-26 20:20 ` [Buildroot] [PATCH 5/5] target/ubifs: Switched to mkfs.ubifs included in mtd-utils Michael Roth
2009-04-02 0:38 ` Hamish Moffatt
-- strict thread matches above, loose matches on Subject: below --
2009-03-26 21:34 [Buildroot] [PATCH v2 0/5] mtd-utils Michael Roth
2009-03-26 21:34 ` [Buildroot] [PATCH 4/5] mtd-utils: Version bump of the GIT source Michael Roth
2009-04-08 20:57 ` Peter Korsgaard
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=20090402004033.GC29488@cloud.net.au \
--to=hamish@cloud.net.au \
--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