From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] util-linux-ng: provide libblkid/libuuid/fsck
Date: Sat, 13 Feb 2010 06:29:53 +0100 [thread overview]
Message-ID: <201002130629.54588.marcin@juszkiewicz.com.pl> (raw)
In-Reply-To: <19c1b8a91002121212lfc08525uc615f845de7160e8@mail.gmail.com>
Dnia piątek, 12 lutego 2010 o 21:12:24 Khem Raj napisał(a):
> > +PR = "${INC_PR}.4"
>
> may be you should start with 0 instead of 4 since its a new recipe.
Will make it on push.
> > +
> > +SRC_URI += "file://uclibc-compile.patch;patch=1\
> > + file://util-linux-ng-replace-siginterrupt.patch;patch=1 \
> > + "
> > +
> > +EXTRA_OECONF += " --enable-libuuid --enable-libblkid \
> > + --enable-fsck"
>
> in this recipe fsck is enabled but 2.16 disables it will that create
> packaging problems for 2.16 now due to changes in util-linux-ng.inc ?
This patchset is more idea then ready to push stuff. I want to solve problem
on blkid/uuid libraries and fsck was just one extra thing. Probably would need
to add some rreplaces/rconflicts stuff.
Today I am leaving for few days - be back on Thursday.
Regards,
--
JID: hrw@jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
next prev parent reply other threads:[~2010-02-13 5:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 14:51 Patches to solve libblkid/libuuid version problems Marcin Juszkiewicz
2010-02-12 14:51 ` [PATCH 1/2] e2fsprogs: stop providing libblkid/libuuid/fsck - they are in util-linux-ng Marcin Juszkiewicz
2010-02-12 15:04 ` Koen Kooi
2010-02-12 14:51 ` [PATCH 2/2] util-linux-ng: provide libblkid/libuuid/fsck Marcin Juszkiewicz
2010-02-12 15:05 ` Koen Kooi
2010-02-12 15:18 ` Marcin Juszkiewicz
2010-02-12 20:12 ` Khem Raj
2010-02-13 5:29 ` Marcin Juszkiewicz [this message]
2010-02-12 20:15 ` Patches to solve libblkid/libuuid version problems Khem Raj
2010-02-13 5:26 ` Marcin Juszkiewicz
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=201002130629.54588.marcin@juszkiewicz.com.pl \
--to=marcin@juszkiewicz.com.pl \
--cc=openembedded-devel@lists.openembedded.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.