From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Removal of e2fsprogs-libs
Date: Wed, 24 Mar 2010 09:35:28 -0700 [thread overview]
Message-ID: <20100324163528.GA15272@gmail.com> (raw)
In-Reply-To: <ac9c93b11003240032h636a60detc59ab859e6fa79c8@mail.gmail.com>
On (24/03/10 08:32), Frans Meulenbroeks wrote:
> 2010/3/23 Graeme Gregory <dp@xora.org.uk>:
> > On Tue, Mar 23, 2010 at 07:01:23PM +0100, Marcin Juszkiewicz wrote:
> >>
> >> During last days I spent a bit of time on e2fsprogs* and util-linux-ng
> >> recipes. They are cleaner now but there is still some work to do.
> >>
> >> We have many recipes which depends on 'e2fsprogs-libs' when they want
> >> 'libblkid' or 'libuuid' which are provided by 'e2fsprogs-libs' and
> >> 'util-linux-ng' recipes. I checked how Debian solves that and got into point
> >> where there is no 'e2fsprogs-libs' recipes in my tree and everything is
> >> building.
> >>
> >> What needs to be changed?
> >>
> >> 1. git rm -r recipes/e2fsprogs-libs
> >> 2. check each recipe which depends on 'e2fsprogs-libs' which library it really
> >> wants
> >> 3. change each recipe which wants 'libblkid' or 'libuuid' to depend on
> >> 'util-linux-ng'
> >> 4. change each recipe which wants 'libcom_err' or 'libss' to depend on
> >> 'e2fsprogs'
> >> 5. add "--with-elf-shlibs" to 'e2fsprogs' to get 'libcom_err' and 'libss'
> >> 6. fix packaging of 'e2fsprogs' to get separate packages for libraries.
> >>
> >> I can work on that in next days but want to inform everyone that such change
> >> will be done.
> >>
> > Hrw thanks for cleaning this up, feel free to add my ack to your completed
> > worked.
>
> Although I highly welcome the cleanup proposed by Marcin, I feel it is
> not proper to submit an ack for patches that are not submitted as
> such.
> Acked-by indicates approval, and I find it somewhat fishy to approve a
> patch that you haven't seen yet.
> (without wanting to question the value or quality of Marcin's work, as
> that will undoubtly be ok).
RFC is request for comment. He is putting forth an idea and wants to know
if its worth. IMO there is nothing wrong in acking the proposal. When the
real code comes around then it can be reviewed for what it does.
Thx
-Khem
>
> Frans
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2010-03-24 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 18:01 [RFC] Removal of e2fsprogs-libs Marcin Juszkiewicz
2010-03-23 18:36 ` Graeme Gregory
2010-03-23 19:41 ` Koen Kooi
2010-03-24 7:32 ` Frans Meulenbroeks
2010-03-24 16:35 ` Khem Raj [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=20100324163528.GA15272@gmail.com \
--to=raj.khem@gmail.com \
--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.