On Wednesday 25 January 2006 21:47, Brian Harring wrote: > On Wed, Jan 25, 2006 at 09:18:28PM +0900, Jason Stubbs wrote: > > There's no other way to do it given repoman's state and the requirements. > > I was talking long term. One time kludges suck (but occur), would like to > see something a bit less short sighted for this though- variants of this > request will come up sooner or later (most likely in the form of can we > warn/error on new commits of deprecated deps). > > Might be wise discussing potential solutions for it.
This is off-topic now. > > If you'd like to make repoman pluggable, convert all the current checks to > > plugins and then make a new plugin for this one and do it all by this > > weekend, be my guest. :P > > Harass antarus, he's been working on integrating swegeners rewrite of > repoman checks (plugins effectively) into mainline repoman. :P > > Besides, a massive change to repoman with 3 days to go is a no go anyways > (kind of limited the choices there) ;) Would 10 days or 17 days really be any different? > > Besides, what's wrong with hardcoded atoms in repoman anyway? > > portage (by extension repoman) is used beyond gentoo. Not everyone may be > at the same step as we are for mod x. End result of hardcoding gentoo > specific crap into repoman is that you force derivatives of gentoo > (vidalinux or genux fex) to start hacking up portage source to remove said > hardcoding. > > Portage exists beyond gentoo; thus gentoo specific hacks should be avoided > when possible. Such as warning/failing on: * the server's repository path is "/space/cvsroot" * any extensions to metadata.xml * larger-than-20k-files * not being copyrighted to Gentoo Foundation * not being distributed under GPLv2 There's probably others but all of those things are Gentoo specific and cause no less trouble than what a virtual/x11 check might cause. > So... long term? Refactor/rewrite/modularize/blah repoman. In the mean time, make do with what we have and let Gentoo derivatives do the same. -- Jason Stubbs -- gentoo-dev@gentoo.org mailing list