On 2011-12-02 10:49, Koen Kooi wrote:
Op 1 dec. 2011, om 17:31 heeft Ulf Samuelsson het volgende geschreven:
2011-12-01 16:37, Koen Kooi skrev:
Op 1 dec. 2011, om 14:16 heeft Philip Balister het volgende geschreven:
On 11/29/2011 03:06 PM, Koen Kooi wrote:
Op 29 nov. 2011, om 20:36 heeft Ulf Samuelsson het volgende geschreven:
On 2011-11-29 16:03, Richard Purdie wrote:
2. "ftp://elsie.nci.nih.gov/pub/tzcode2011i.tar.gz";
is no longer
available.
tzdata , same problem.
The recipe is located in two places.
meta-openembedded/meta-oe/recipes-extended/tz*/tz*.bb have the
problem
This is what the build uses.
This is something to raise with the meta-oe maintainers. I think there
isn't a problem in OECore.
Since we now have a large number of layers, maybe it is a good
idea to define in each layer, how the "git send email" should behave in
by providing a better ".git/config" file in the trunk?
I.E:
[sendemail]
to =
openembedded-core@lists.openembedded.org
or
meta-angstrom/.git/config
[sendemail]
to =
angstrom-distro-de...@linuxtogo.org
[format]
subjectprefix = "[meta-angstrom]"
No need to look in the README file with this.
That assumes git-send-email is the preferred way, which it isn;'t for a lot of
layers
Even if it is not the preferred way, it would direct the discussion to
the appropriate list. This would reduce the number of mis-directed
emails to this list.
You can't fix stupid, sadly.
Tend to disagree.
The whole purpose of OE is to make it possible for people,
stupid or not, to go off and make things which they would
not be able to do on their own.
As I see it, it is no real drawback of adding this, and at least some benefit.
The drawback is that people will postpone reading the README even longer.
Why are you so dead against having people read the README?
I am against that every layer should *appear to* have their own way of
treating feedback.
There should be a common README on how to provide a patch, and any
difference in where it ends up should be hidden in the system.
This will make it easy for the causal user of a layer.
If you want stuff to be pulled, then there are ways of handling this.
Instead of directing the email to a list, you could direct the mail
to a special address, which bounces back a message saying that
the recommended thing is to pull.
It could of course forward to the real list as well.
As mentioned before by me, and by Frans right now, If I have to set up a
git mirror
for something I dont use (like meta-ti right now),
just because this has a problem which affects my builds, I won't do that.
As I dig deeper into openembedded-core, I will probably get
to setting up git mirrors for the layers I use.
OTOH , If I am bored and pull up my Beagleboard from a drawer, again
I would probably do a git mirror for meta-ti.
Some further study shows that the idea will not work as intended fully.
meta-openembedded and meta-handhelds have "meta-*" subdirectories
which each have their own README with different instructions for the
same git tree.
Seems kind of strange to me.
BR
Ulf Samuelsson
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Best Regards
Ulf Samuelsson
eMagii
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
