The Enlightenment project switched from CVS to SVN.
Therefor the enlightenment.eclass in portage needs to be updated to use SVN.
Steps to Reproduce:
1. layman -a enlightenment
2. emerge e (-9999 versions)
Tries to pull from non-existant CVS repo
Should pull from new SVN
Created attachment 165570 [details, diff]
Works for me, if any ECVS_MODULE definitions are removed from the e_modules-* ebuilds in the overlay.
Lot of of things got moved around in SVN though, so the ebuilds in the overlay need more fixing. Snapshots and the ebuilds in portage should be fine though.
Created attachment 165585 [details, diff]
I broke the E17_ESVN_REPO_URI override (ex E17_ECVS_SERVER). Fixed patch.
Not sure if this is still needed/makes sense at all.
I modified the ebuilds and eclass some time ago and sent an e-mail with the diffs to he who I thought was the maintainer... never got a reply.
(In reply to comment #3)
> I modified the ebuilds and eclass some time ago and sent an e-mail with the
> diffs to he who I thought was the maintainer... never got a reply.
Since this is an overlay, you need not be a Gentoo developer to help out. You just need to not suck. If you think you do not suck and you'd like to help, please drop me a line Mike Frysinger with your overlay username.
I checked all ebuilds to make them match new source tree structure, and also made a few modifications in eclass to make it svn-compatible. Only problem, which makes it non-ready for end-user - is broken CVS-compatibility, which brokes a few CVS-hosted external projects, which was served with enlightenment.eclass before. You can browse and checkout my overlay (svn) freely:
(thanks to Vadim Efimof for domain name, I don't have any yet)
Now both CVS and SVN repositories supported. Ebuild changes still needed.
(In reply to comment #6)
> Now both CVS and SVN repositories supported. Ebuild changes still needed.
Great job guys!
I renewed recently. There were no any issues during compiling.
8 month's bug has been corrected - battery module.
Since it's not vapier overlay, we could put where any missed modules and applications.
This is not a really good idea - to clone repository, if you mean this. This is only a temporary workplace, when it will be good enough, we plan to contact vapier (aka SpanKY) for syncing it with main overlay. Of course, if you have any ebuilds (or just any info) for missing packages - any help are welcome.
While all packages are _fetching_ successfully, we not test their's compilation. All tree must be reviewed and some stuff, like evidence, which e17 support are completelly broken, must be removed,
If you guys have a better/more mature/smarter eclass than the one above, you should attach the patch to the original here.
Linking to external repos is somehwhat disliked IIRC.
I wish I could, but this is useless. Our eclass need changes in all ebuilds. I could produce a patch for all overlay, but it will be quite big
(In reply to comment #10)
> I wish I could, but this is useless. Our eclass need changes in all ebuilds. I
> could produce a patch for all overlay, but it will be quite big
Sounds complicated. Mine only needs changes for e_modules-* (just remove ECVS_MODULE statements) and things that got moved in SVN, like for example epeg:
No idea what's the point to support both, CVS and SVN, as stuff that is not part of the enlightenment project and its SVN repo, doesn't really need to use enlightenment.eclass - see itask-ng/winlist-ng ebuilds in the overlay..
Just use standard cvs.eclass there.. *shrug*
Yeah. That's right. But you need to do this changes in every ebuild.
Also - eclass with CVS support is better that eclass without it (If this support do not require too much code complification, of course), some things still use CVS and some may be added in future.
Created attachment 165867 [details, diff]
enlightenment.eclass with both SVN and CVS support diff.
Could you give an example of an ebuild that still uses (enlightenment) CVS, as I fail to find one.
For now - only app-misc/evidence =). But, even it will be deleted (due to completelly broken e17 support), there is chance that some other CVS modules will be included later (or already included in some other overlays). We was acting in way of providing full backward-compatibility, to make sure, that any changes in eclass will not break anything (exept overlays packets). Later, maybe, CVS support will be deleted.
should be fixed in cvs now