From: Martin Jansa <martin.jansa@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v5] netbase: split up in netbase and init-ifupdown
Date: Wed, 6 Feb 2013 11:14:42 +0100 [thread overview]
Message-ID: <20130206101442.GS3271@jama> (raw)
In-Reply-To: <5112293F.4080503@mlbassoc.com>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
On Wed, Feb 06, 2013 at 02:58:23AM -0700, Gary Thomas wrote:
> On 2013-02-05 06:14, Otavio Salvador wrote:
> > On Tue, Feb 5, 2013 at 8:29 AM, Gary Thomas <gary@mlbassoc.com> wrote:
> >> On 2013-02-04 08:12, Constantin Musca wrote:
> >>>
> >>> - netbase should only include etc-rpc, etc-protocols, etc-services
> >>> and the hosts file
> >>> - the init script/configuration files should be in another package
> >>> (init-ifupdown)
> >>
> >>
> >> What is the benefit of such an intrusive change?
> >> Why not just have the netbase recipe create a separate package?
> >
> > Many images use different network managers so ifupdown might not be
> > need; thus the split. Is it what you're concerned about?
>
> The massive renames and new recipe. I think it should be possible
> to split the ifup/ifdown functions and keep the 'netbase' recipe.
But ifup/ifdown are sometimes MACHINE_ARCH and the rest is TUNE_PKGARCH.
So it makes sense to split them.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2013-02-06 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 15:12 [PATCH v5] netbase: split up in netbase and init-ifupdown Constantin Musca
2013-02-04 14:31 ` Martin Jansa
2013-02-05 10:29 ` Gary Thomas
2013-02-05 13:14 ` Otavio Salvador
2013-02-06 9:58 ` Gary Thomas
2013-02-06 10:14 ` Martin Jansa [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=20130206101442.GS3271@jama \
--to=martin.jansa@gmail.com \
--cc=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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