From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][meta-networking][PATCH V2 3/3] ntp: Clean up recipes
Date: Thu, 1 Nov 2012 10:31:14 -0400 [thread overview]
Message-ID: <20121101143114.GF4673@windriver.com> (raw)
In-Reply-To: <50920DAB.7070206@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
[Re: [oe] [meta-oe][meta-networking][PATCH V2 3/3] ntp: Clean up recipes] On 12.11.01 (Thu 06:50) Martin Ertsås wrote:
> On 11/01/12 02:08, Paul Eggleton wrote:
> >On Tuesday 23 October 2012 12:20:20 Morgan Little wrote:
> >>-PACKAGES += "ntpdate ${PN}-bin ${PN}-tickadj ${PN}-utils"
> >...
> >>+PACKAGES += "${PN}-date ${PN}-bin ${PN}-tickadj ${PN}-utils"
> >I'm not particularly happy with this change. Apart from the fact that it
> >wasn't mentioned in the commit message, it breaks any recipe that depends upon
> >the previous ntpdate package. Could we go back to the old ntpdate name for the
> >package or at the very least provide an RPROVIDES for the old name? I'm happy
> >to submit a patch to do this once there is agreement either way.
> >
> >Cheers,
> >Paul
> >
> I agree with you. Also find it kind of strange to change from
> ntpdate to ntp-date, as the universally known name of that module is
> ntpdate. Don't really see the rational of changing that to ntp-date
> in the recipe.
Agreed. Though if there's a good reason to rename in ntp-date, that's
fine with me, so long as we go with Paul's suggestion of having an
RPROVIDES for ntpdate. It's probably best to leave it as ntpdate,
though.
--
Joe MacDonald, Sr. Member of Technical Staff, Linux Products Group, Wind River
direct 613.270.5750 mobile 613.291.7421 fax 613.592.2283
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-11-01 14:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 16:20 [meta-oe][meta-networking][PATCH V2 0/3] ntp updates Morgan Little
2012-10-23 16:20 ` [meta-oe][meta-networking][PATCH V2 1/3] ntp: Move from meta-oe to meta-networking Morgan Little
2012-10-23 16:20 ` [meta-oe][meta-networking][PATCH V2 2/3] ntp: Uprev from 4.2.6p3 to 4.2.6p5 Morgan Little
2012-10-23 16:20 ` [meta-oe][meta-networking][PATCH V2 3/3] ntp: Clean up recipes Morgan Little
2012-11-01 1:08 ` Paul Eggleton
2012-11-01 5:50 ` Martin Ertsås
2012-11-01 14:31 ` Joe MacDonald [this message]
2012-11-01 17:09 ` Little, Morgan
2012-11-01 17:19 ` Paul Eggleton
2012-11-01 17:32 ` Joe MacDonald
2012-11-02 7:00 ` Martin Ertsås
2012-11-02 13:01 ` Joe MacDonald
2012-11-02 13:09 ` Martin Ertsås
2012-11-02 13:14 ` Joe MacDonald
2012-11-02 9:59 ` Paul Eggleton
2012-11-02 13:07 ` Joe MacDonald
2012-11-02 13:38 ` Paul Eggleton
2012-11-02 14:02 ` Joe MacDonald
2012-11-02 14:10 ` Paul Eggleton
2012-11-02 14:14 ` Joe MacDonald
2012-11-02 17:26 ` Paul Eggleton
2012-11-04 18:43 ` Joe MacDonald
2012-11-09 14:55 ` Little, Morgan
2012-11-09 15:04 ` Joe MacDonald
2012-11-10 13:22 ` Paul Eggleton
2012-11-02 21:09 ` Phil Blundell
2012-11-02 15:44 ` Phil Blundell
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=20121101143114.GF4673@windriver.com \
--to=joe.macdonald@windriver.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.