From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Cc: Michael 'Mickey' Lauer <mickey@openmoko.org>
Subject: Re: The ongoing SRCREV saga
Date: Thu, 13 Sep 2007 09:55:59 +0200 [thread overview]
Message-ID: <46E8ED0F.5000003@student.utwente.nl> (raw)
In-Reply-To: <1189638097.6480.132.camel@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Richard Purdie schreef:
> [This was meant for the OE list and autocomplete didn't quite do what
> I'd intended with the recipients originally, sorry :/]
>
> There is a certain amount of friction in the community regarding the
> recent SRCREV additions of which I've received my share.
>
> The concerns are really about how we're using SRCREV in OE rather than
> about the bitbake implementation itself which is an important
> distinction.
>
> The basic problem is that people view the change as making parsing
> dependent on network access which was never the intent. If people added
> a revision to sane-srcrevs.inc every time they added a SRCREV based .bb
> file we wouldn't have a problem and parsing never would depend on
> network access. I'm living on another planet if I expect that to happen
> in reality though so this approach simply isn't going to work though.
>
> I'm therefore proposing we change bitbake.conf to read:
>
> SRCREV = "1"
>
> This puts an end to network access when a SRCREV hasn't been set in
> sane-srcrevs.inc. Anyone wishing to default to svn head in these cases
> can add this to local.conf (or their distro):
>
> SRCREV = "${AUTOREV}"
or 'require conf/distro/insane-srcrevs.inc'
> I propose keeping sane-srcrevs.inc for distros to include to have
> meaningful revisions for srcrev based packages.
Angstrom includes it now by default.
> If a distro like openmoko wants to make cutting edge development
> possible I suggest creating a .inc file which sets
>
> SRCREV-pn-whatever = "${AUTOREV}"
'require conf/distro/include/moko-autorev.inc'
> for the packages they want to make floating.
>
> I firmly believe that floating SRCREVs should be opt in and these
> changes allow that whilst still letting distros or users make use of
> floating versions. I'd also advise openmoko against making SRCREV =
> "${AUTOREV}" the default and to only make the packages they need
> floating but thats not my call to make :).
>
> Are there any objections to the above? I'll probably commit this fairly
> quickly if the openmoko devs are agreeable.
Mickey OK'ed it on another list, so I added sane-srcrevs.inc to angstrom. (in)sane-srcrevs
and moko-autorev needs some tweaking, but 90% is there.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFG6O0PMkyGM64RGpERAuaOAKCnIGW1yzZu0yh+Qd8vzvDP3LUhWwCdE48L
wR/Y3/kaYE9SPiuKNz0aqas=
=oeJo
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-09-13 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 23:01 The ongoing SRCREV saga Richard Purdie
2007-09-13 1:30 ` mwester
2007-09-13 7:55 ` Koen Kooi [this message]
2007-09-13 8:45 ` Richard Purdie
[not found] <1189635624.6480.129.camel@localhost.localdomain>
2007-09-12 23:47 ` Michael 'Mickey' Lauer
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=46E8ED0F.5000003@student.utwente.nl \
--to=k.kooi@student.utwente.nl \
--cc=mickey@openmoko.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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