Maybe I'm missing something here but  what does this do that the current 
ebuilds that access CVS don't do?  The current ebuilds - using the CVS eclass 
fetch the most current CVS version, then you do whatever you need to do just 
like a regular ebuild.   If  you  need the updated CVS you just emerge again.

> 
> From: Timo Horstschäfer <[EMAIL PROTECTED]>
> Date: 2005/06/01 Wed PM 03:13:44 EDT
> To: gentoo-dev@lists.gentoo.org
> Subject: [gentoo-dev] cvs-ebuilds
> 
> A few day ago i thought about ebuilds without a version number.
> The thing is to fetch all files via cvs and then do the things you do
> with a normal ebuild.
> 
> After fetching the files all the content will be packed into a bz2
> archive and saved in /usr/portage/distfiles/
> i.e. if i emerge again the stored bz2archive will be extracted and
> synced with cvs again.
> So i can always can get the newest version without waiting for an ebuild.
> 
> Of course those packages are marked ~* anytime and nobody can promise,
> the compiling won't fail.
> 
> Another feature could be to save the bz2 archive with the date of
> fetching in its name.
> Then i could use an old archive if there is i great bug in the newest files.
> 
> I want to read some opinions about this, it's just an idea.
> 
> -- 
> gentoo-dev@gentoo.org mailing list
> 
> 

-- 
gentoo-dev@gentoo.org mailing list

Reply via email to