Overlay ideas

Hi all, 

With regard to the (user) overlays that are supposed to be
merged into
the main prefix tree, I came up with the following idea the
other day.

The main problem is that merging apps from the overlays into
the prefix
tree, is that currently it's not obvious what the changes
are.  Some
(hopefully most) ebuilds are just imported, and eapify did
the trick,
while others need some little or heavy patching.

The idea I came up with is based on the "notes"
file idea.  All ebuilds
in an overlay should have a "notes" file
describing what had to be
changed.  This immediately excludes all packages that didn't
need
anything after eapify.

Some more formal, I propose to:
- describe changes made to the ebuild in a "notes"
file in the ebuild
  directory
  * changes such as added patches
  * changes such as hacks in the ebuild to get EPREFIX
support right
  * don't make notes for keywords!
  * whether it works or not!
- if you import an ebuild, and just run eapify, add your
keyword and
  commit, don't add a notes file!

This allows to quickly see what are the trivial packages,
and which are
the harder "nuts to crack".

Comments, anyone?

-- 
Fabian Groffen
Gentoo on a different level
-- 
gentoo-altgentoo.org mailing list

On Feb 25, 2007, at 11:28 , Fabian Groffen wrote:

> The idea I came up with is based on the
"notes" file idea. All ebuilds
> in an overlay should have a "notes" file
describing what had to be
> changed. This immediately excludes all packages that
didn't need
> anything after eapify.
>
> Some more formal, I propose to:
> - describe changes made to the ebuild in a
"notes" file in the ebuild
>   directory
>   * changes such as added patches
>   * changes such as hacks in the ebuild to get EPREFIX
support right
>   * don't make notes for keywords!
>   * whether it works or not!
> - if you import an ebuild, and just run eapify, add
your keyword and
>   commit, don't add a notes file!
>
> This allows to quickly see what are the trivial
packages, and which are
> the harder "nuts to crack".
>
> Comments, anyone?

I tried this on app-editors/nedit in the unofficial
overlay.  Is this 
what you had in mind?

// Cheers; Johan

--
gentoo-altgentoo.org mailing list

On 27-02-2007 16:47:03 +0100, Johan Hattne wrote:
> On Feb 25, 2007, at 11:28 , Fabian Groffen wrote:
> 
> >The idea I came up with is based on the
"notes" file idea. All ebuilds
> >in an overlay should have a "notes" file
describing what had to be
> >changed. This immediately excludes all packages
that didn't need
> >anything after eapify.
> >
> >Some more formal, I propose to:
> >- describe changes made to the ebuild in a
"notes" file in the ebuild
> >  directory
> >  * changes such as added patches
> >  * changes such as hacks in the ebuild to get
EPREFIX support right
> >  * don't make notes for keywords!
> >  * whether it works or not!
> >- if you import an ebuild, and just run eapify, add
your keyword and
> >  commit, don't add a notes file!
> >
> >This allows to quickly see what are the trivial
packages, and which are
> >the harder "nuts to crack".
> >
> >Comments, anyone?
> 
> I tried this on app-editors/nedit in the unofficial
overlay.  Is this 
> what you had in mind?

Yeah.  I don't agree with the points, but it's very nice!


-- 
Fabian Groffen
Gentoo on a different level

-- 
gentoo-altgentoo.org mailing list