* [gentoo-dev] cvs-ebuilds
@ 2005-06-01 19:13 Timo Horstschäfer
2005-06-01 19:20 ` Mike Frysinger
0 siblings, 1 reply; 3+ messages in thread
From: Timo Horstschäfer @ 2005-06-01 19:13 UTC (permalink / raw
To: gentoo-dev
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-dev] cvs-ebuilds
2005-06-01 19:13 Timo Horstschäfer
@ 2005-06-01 19:20 ` Mike Frysinger
0 siblings, 0 replies; 3+ messages in thread
From: Mike Frysinger @ 2005-06-01 19:20 UTC (permalink / raw
To: gentoo-dev
On Wednesday 01 June 2005 03:13 pm, Timo Horstschäfer wrote:
> A few day ago i thought about ebuilds without a version number.
there's a bug open atm to get a '_cvs' version tag to go along with '_alpha',
'_beta', and all that but development of it has been slow (or not at all)
> The thing is to fetch all files via cvs and then do the things you do
> with a normal ebuild.
how does any of this differ from the cvs eclass ? (emerge portage-manpages &&
man cvs.eclass)
-mike
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-dev] cvs-ebuilds
@ 2005-06-01 19:51 brettholcomb
0 siblings, 0 replies; 3+ messages in thread
From: brettholcomb @ 2005-06-01 19:51 UTC (permalink / raw
To: gentoo-dev
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 <timo.horstschaefer@gmail.com>
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-06-01 19:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-06-01 19:51 [gentoo-dev] cvs-ebuilds brettholcomb
-- strict thread matches above, loose matches on Subject: below --
2005-06-01 19:13 Timo Horstschäfer
2005-06-01 19:20 ` Mike Frysinger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox