git-2.eclass is in the tree for a while now, and there's still awful
lot of packages using old & deprecated git.eclass.
Why migrate?
- git-2 supports fallback SRC_URIs -- you can set it to prefer git://
but fallback to http:// if git is unreachable (e.g. due to firewall),
- git-2 is cleaner and has a better design (no more src_prepare()!),
- git-2 handles submodules better,
- git.eclass is no longer supported and will go away.
I'm attaching a list of packages still using git.eclass, grouped by
herds and maintainers.
Additional resources:
- list of packages using git.eclass [1],
- devmanual entry for git-2.eclass [2],
- an example ebuild for a git.overlays.g.o package [3],
- an example ebuild for a github package [4].
On 6/24/11 11:35 PM, Michał Górny wrote:
> Hello,
>
> git-2.eclass is in the tree for a while now, and there's still awful
> lot of packages using old & deprecated git.eclass.
>
> Why migrate?
Hi,
What are the pitfalls during migration? Or is it just /git/git-2/ ?
Thanks jusitn
06-25-2011, 07:40 AM
Michał Górny
Please migrate to git-2.eclass
On Sat, 25 Jun 2011 09:11:16 +0200
justin <jlec@gentoo.org> wrote:
> On 6/24/11 11:35 PM, Michał Górny wrote:
> > Hello,
> >
> > git-2.eclass is in the tree for a while now, and there's still awful
> > lot of packages using old & deprecated git.eclass.
> >
> > Why migrate?
>
> What are the pitfalls during migration? Or is it just /git/git-2/ ?
In the most common case, yes. But you are advised to add a http
fallback in EGIT_REPO_URI.
Other API changes are:
- EGIT_*_CMD is no longer overridable,
- src_prepare() is no longer exported (EGIT_BOOTSTRAP is called
in src_unpack() but I don't recommend that, EGIT_PATCHES gone),
- EGIT_QUIET gone, EGIT_UNPACK_DIR gone (changes to other vars prolly).
So I think most of these won't apply to the ebuilds, maybe the second
one.
--
Best regards,
Michał Górny
06-25-2011, 07:56 AM
Nikos Chantziaras
Please migrate to git-2.eclass
On 06/25/2011 12:35 AM, Michał Górny wrote:
Hello,
git-2.eclass is in the tree for a while now, and there's still awful
lot of packages using old& deprecated git.eclass.
I think I remember seeing deprecation warnings in the past when an
ebuild was using a deprecated eclass (right at the beginning when the
emerge starts.) Perhaps it would be a good idea to add one of those in
git.eclass.
06-25-2011, 02:20 PM
Nirbheek Chauhan
Please migrate to git-2.eclass
On Sat, Jun 25, 2011 at 1:26 PM, Nikos Chantziaras <realnc@arcor.de> wrote:
> On 06/25/2011 12:35 AM, Michał Górny wrote:
>>
>> Hello,
>>
>> git-2.eclass is in the tree for a while now, and there's still awful
>> lot of packages using old& Â*deprecated git.eclass.
>
> I think I remember seeing deprecation warnings in the past when an ebuild
> was using a deprecated eclass (right at the beginning when the emerge
> starts.) Â*Perhaps it would be a good idea to add one of those in git.eclass.
>
That's a horribly bad idea. Users should never need to see such
things. The example you're thinking of is python.eclass, and that
resulted in confused users filing bug reports.
There's currently a repoman warning for git.eclass usage, and that suffices.