KDE CVS/Subversion Split Ebuilds (Replies Part 1)

[Bonkie]

Looks good
You forgot to include "eval unsermake_setup" in kde_meta_src_install()

[mario]

[jsrlepage]

i can't seem to emerge anything with the ebuilds... why?

error :

[mario]

[jsrlepage]

here is the listing :

[mario]

When was the last time you gensynced???

[jsrlepage]

yesterday?

EDIT :

[mario]

There must be a discrepancy between the two paths, what kind of system is this? Can you post emerge --info?

[jsrlepage]

hacky system, highly experimental.

you can clearly see that my portage was hacked by myself, and that I have unlocked barry from the programmer's clutches

[mario]

[mario]

[ktech]

After weeks of not compiling kradio (wasn't working), I've readed that it needs unsermake to compile, so I enabled it in make.conf (features) and then I do an:

[jsrlepage]

after a manual CO, here is what i get :

[Bonkie]

[jsrlepage]

[Bonkie]

[jsrlepage]

well, for all i know, it borks still. after 20 mins... boo-hoo.

edit : still after one hour!
_________________
cybikbase::~cybik()

[Bonkie]

LIke mario said;

modify <overlay>/eclass/subversion.eclass and add to this function:

[jsrlepage]

there :

[Bonkie]

Just added ability to set autoskipcvs in FEATURES.
If you set this, the ebuild will check if the repositoy's revision is different then the local revision, and if it's NOT, it will exit. I advise you to only use this in specific cases (like scripts) and not setting this as default in /etc/make.conf !

Some more notes

• There is no way I could stop the ebuild (if revision has not changed) without merging the sanbox to the filesystem (and we don't want that because nothing was compiled and installed). So now it will exit with an error, meaning the sandbox doesn't get removed (in /var/tmp/portage) and if you specified a list of apps to be compiled, it will stop with the one that procuded the error. However the latter is easily worked around with a bash for loop
  

  Code:

  for i in ${LIST} ; do emerge ${i} ; done

  
  
• The order in which the ebuilds are processed is crucial; Everything is checked in the same local working copy, and since there are ebuilds that also fetch other modules' sources, you want to emerge the other modules first. Or else, since the revisison is already up to date, it will not compile and install, although the previous ebuild didn't take care of that. For example, kcontrol also fetches kicker, among others, so specify kicker before kcontrol, or else kicker will never be compiled because kcontrol updated the revision !
  

I was also working on a script that updates all KDE (and other svn-) packages installed: scripts/updateKDEsvn
It merges all modules in the correct order, with autoskipcvs set, but only those you have already installed, meaning it will not install new KDE apps (instead of course for new dependancies). Feel free to modify I would like to ask though, that when using it, people could look out for bad package order ?? I haven't installed every KDE app, so it could be possible there's still some packages that pre-fetch source for other modules, and we don't want that ... Let me know so I can change it

[edit:] Oops, forgot to mention that the script uses equery (from app-portage/gentoolkit) to check if a package is installed or not, so either modify the script or install gentoolkit if you haven't already (it comes with some other nice apps, like euse).
_________________
"I would say we have a 50% chance of survival, but I consider myself an optimist so I'll give us 50,5% ..."
~ Arthur C. Clarke [Physics PHD,SF Writer], when asked about the chances of the human race's survival

[superstoned]

whow, bonky, you're the man. nice going

i'm in the process of installing gentoo again, but it'll be ready soon (ahem, still some 200 kde packages left to-do...).

[Husky]

updated version of the kopete ebuild:

[mario]

Wow,

I just came back from a 3-day trip and am running updateKDEsvn now

Thanks a lot!!!

[Bonkie]

[Husky]