From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 3/3] base.bbclass: fix base_get_scmbasepath() to look for recipes/ and fall back to packages/ while parsing BBFILES
Date: Mon, 23 Mar 2009 14:12:03 -0400 [thread overview]
Message-ID: <49C7D0F3.5040803@balister.org> (raw)
In-Reply-To: <be7a9f3d0903231104u632d2961w7e84e21a1f9bbd1f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
Otavio Salvador wrote:
> On Mon, Mar 23, 2009 at 1:21 PM, Denys Dmytriyenko <denis@denix.org> wrote:
>> On Mon, Mar 23, 2009 at 05:57:27AM -0300, Otavio Salvador wrote:
>>> Denys Dmytriyenko <denis@denix.org> writes:
>>> In my opinion, while it makes life easier the result of it is mixed
>>> environments.
>>>
>>> I'm still using packages/ in our local distro and I haven't yet found
>>> the time to merge current tree since we've a lot of local recipes that
>>> will break and this change could make it simple but I still refrain
>>> about having it included.
>>>
>>> It looks like the logical thing is kind of "force" people to handle it.
>> First you said you are not ready to make the switch, and then you are saying
>> we need to force people into it... :)
>
> Well me not being ready to make the switch is due our deadlines. This doesn't
> change my general idea about forcing people to handle it and avoid those
> "backward compatibility hacks" to stay forever ;-)
>
>> Anyway, it doesn't matter anymore, as this code has been replaced completely
>> by one of kergoth's recent commits.
>
> Oh! I didn't see it. Please archive it in PatchWork then :-D
You should be able to change the flag yourself. When people create
accounts on Patchwork, I set them to allow them to change patch states.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2009-03-23 18:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 23:32 [PATCH 0/3] rename packages/ to recipes/ per earlier agreement Denys Dmytriyenko
2009-03-16 23:32 ` [PATCH 1/3] " Denys Dmytriyenko
2009-03-16 23:32 ` [PATCH 2/3] recipes: fix hardcoded instances of packages/ Denys Dmytriyenko
2009-03-17 2:45 ` Khem Raj
2009-03-16 23:32 ` [PATCH 3/3] base.bbclass: fix base_get_scmbasepath() to look for recipes/ and fall back to packages/ while parsing BBFILES Denys Dmytriyenko
2009-03-23 8:57 ` Otavio Salvador
2009-03-23 16:21 ` Denys Dmytriyenko
2009-03-23 18:04 ` Otavio Salvador
2009-03-23 18:12 ` Philip Balister [this message]
2009-03-16 23:32 ` Denys Dmytriyenko
2009-03-17 0:56 ` [PATCH 0/3] rename packages/ to recipes/ per earlier agreement Mike (mwester)
2009-03-17 1:25 ` Philip Balister
2009-03-17 19:26 ` Denys Dmytriyenko
2009-03-19 0:25 ` Theodore A. Roth
2009-03-19 2:01 ` Denys Dmytriyenko
2009-03-19 3:13 ` Denys Dmytriyenko
2009-03-19 7:22 ` Frans Meulenbroeks
2009-03-19 17:05 ` Theodore A. Roth
2009-03-19 20:33 ` Frans Meulenbroeks
2009-03-17 13:09 ` Marcin Juszkiewicz
2009-03-17 14:42 ` Koen Kooi
2009-03-17 17:19 ` Frans Meulenbroeks
2009-03-17 19:54 ` Otavio Salvador
2009-03-17 19:59 ` Denys Dmytriyenko
2009-03-17 19:29 ` Denys Dmytriyenko
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=49C7D0F3.5040803@balister.org \
--to=philip@balister.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox