Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: superfluous download locations in oe-core's bitbake.conf
Date: Fri, 22 Jun 2012 14:34:13 +0100	[thread overview]
Message-ID: <25294393.hmh001VYMW@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1206210454080.17361@oneiric>

On Thursday 21 June 2012 04:56:51 Robert P. J. Day wrote:
>   given that oe-core is defined as being a really minimal
> configuration with no extraneous cruft, there seems to be a number of
> unnecessary download locations in the shipped bitbake.conf, things
> like:
> 
> ADOBE_MIRROR =
> FREEBSD_MIRROR =
> 
> and so on.  obviously, they're not doing any harm but there seems to
> be little value in defining download locations that aren't used by
> anything actually in oe-core.

These are present for largely historical reasons - namely in OE-Classic we had 
a number of recipes needing this same mirror defined and it was deemed that it 
was easier to edit it in one place if it needed to change. Some of them are 
even completely useless now as the sites to which they point are now gone, 
e.g. HANDHELDS_CVS.

I think the way to approach this would be to just submit a patch removing the 
more extraneous ones and see if anyone complains. Note that some of them that 
aren't used in OE-Core might be used within meta-oe or other OE community 
layers, so those might need to stay at least for the time being.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-06-22 13:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21  8:56 superfluous download locations in oe-core's bitbake.conf Robert P. J. Day
2012-06-22 13:34 ` Paul Eggleton [this message]
2012-06-22 14:24   ` Richard Purdie
2012-06-22 14:38     ` Martin Jansa
2012-06-22 14:45       ` Paul Eggleton
2012-06-22 15:20   ` Robert P. J. Day

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=25294393.hmh001VYMW@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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