On Friday 18 February 2005 16:00, Pavel Volkovitskiy wrote: > With CVS i would like to compile KDE_3_4_BRANCH (for example), not HEAD With classic cvs ebuilds that would mean maintaining several sets of cvs ebuilds, one per kde branch (the HEAD set becoming the next branch set).
It'd be a lot easier to support USE=cvs or FEATURES=cvs or just $KDECVS, that would make the eclasses fetch source from cvs, leaving src_compile etc alone. (Although we'd have to deal with patch management somehow... A lot of patches won't apply against a moving CVS target, or would already be applied upstream). But some people might complain as that'd put kde-cvs functionality in portage and make it even easier for users to abuse it :-) (Of course it'd be completely unsupported, but when did that ever stop anyone?) In any case, I don't intend working on kde cvs ebuilds again until after 3.4.0 and maybe not then. Although, they'd be a big help with a release like 4.0, which ought to include many differences from 3.x. > I think it's will be great if the package version will be depended on > build time Can't be done with current portage. -- Dan Armak Gentoo Linux developer (KDE) Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD 0069 508D 9143 8D5F 8951
pgpRcmQpkZQ2P.pgp
Description: PGP signature
