From: "Øyvind Repvik" <repvik@kynisk.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: More granular libraries packaging
Date: Sat, 28 Oct 2006 03:12:05 +0200 [thread overview]
Message-ID: <4542AE65.2040102@kynisk.com> (raw)
In-Reply-To: <1161978194.1649.335.camel@gandalf.tm.informatik.uni-frankfurt.de>
Michael 'Mickey' Lauer wrote:
> Am Freitag, den 27.10.2006, 18:01 +0200 schrieb Marcin Juszkiewicz:
>> My proposition is - let split each library to separate package. This will
>> enlarge feeds (so ipkg will get hurt more ;( but in some situations can
>> give us smaller rootfs.
>
> +1 from me, however would this be explicit or implicit, i.e. do we need
> to opt-in for it to happen (e.g. by inheriting package_libs) or do we
> need to opt-out for it _not_ to happen (e.g. by defining
> PACKAGE_LIBS_AUTOMATIC = "0").
I wouldn't mind it being opt-out, since that makes it somewhat easier
(imho) to figure out which packages "break" with this change.
Regards,
Øyvind "NAiL" Repvik
next prev parent reply other threads:[~2006-10-28 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 16:01 RFC: More granular libraries packaging Marcin Juszkiewicz
2006-10-27 19:43 ` Michael 'Mickey' Lauer
2006-10-28 1:12 ` Øyvind Repvik [this message]
2006-10-31 16:17 ` Richard Purdie
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=4542AE65.2040102@kynisk.com \
--to=repvik@kynisk.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.