Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Cleanup / janitors
Date: Tue, 16 Feb 2010 10:41:17 +0100	[thread overview]
Message-ID: <hldp7r$l5b$1@ger.gmane.org> (raw)
In-Reply-To: <ac9c93b11002160039j717d1611wbdd1d2fac220dd55@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 16-02-10 09:39, Frans Meulenbroeks wrote:
> 2010/2/16 Koen Kooi <k.kooi@student.utwente.nl>:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 16-02-10 00:38, Chris Larson wrote:
>>> Greetings all,
>>>
>>> Per discussion in the TSC meeting this month, I'm sending out this email as
>>> a probe.  Would anyone on the list benefit from a "janitors" type project,
>>> to outline and document specific cleanup tasks and how they should be done?
>>> There are many tasks that need doing which involve editing of large amounts
>>> of files in relatively simple ways, and I suspect, but am not yet certain,
>>> that there are a group of individuals who wish to contribute to the project,
>>> but are new enough that they don't feel confident diving into anything
>>> invasive.  This sort of a task could be a starting point for that sort of
>>> individual.  Thoughts?  Anyone out there in that camp currently that would
>>> benefit from something like this?
>>
>> The first project that comes to mind is converting simple recipes (e.g.
>> not perl) to new style staging. It's a fairly simple job that has a huge
>> impact.
> 
> Problem is to do that reliable.
> It is easy to remove the do_stage section from a recipe, and it is
> easy to verify that it builds, but it is already becoming less trivial
> to verify that everything that depends on it builds too,

A simpile first step is:

1) build recipe
2) bump PR
3) fix staging
4) build recipe
5) diff the 2 packaged-staging recipes

If the result of 4) is a superset of 1) then you most likely did the
right thing.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLemg9MkyGM64RGpERAsJhAKCVNBO2i/El72HF3YNgz9qdm8QenQCfbwg9
g2/Zq8mnEUP7Z5OqNdYX7xA=
=pT6Y
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2010-02-16  9:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 23:38 Cleanup / janitors Chris Larson
2010-02-16  8:13 ` Koen Kooi
2010-02-16  8:39   ` Frans Meulenbroeks
2010-02-16  9:08     ` Andrea Adami
2010-02-16  9:18       ` Richard Purdie
2010-02-16  9:19     ` Richard Purdie
2010-02-17 15:39       ` contrib tree (was: Cleanup / janitors) Rolf Leggewie
2010-02-16  9:41     ` Koen Kooi [this message]
2010-02-16 23:30     ` Cleanup / janitors Tom Rini
2010-02-17  0:57       ` Chris Larson

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='hldp7r$l5b$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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