From: "Timo Horstschäfer" <timo.horstschaefer@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] cvs-ebuilds
Date: Wed, 1 Jun 2005 21:13:44 +0200 [thread overview]
Message-ID: <ba583fdd05060112135019f7a9@mail.gmail.com> (raw)
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
next reply other threads:[~2005-06-01 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 19:13 Timo Horstschäfer [this message]
2005-06-01 19:20 ` [gentoo-dev] cvs-ebuilds Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2005-06-01 19:51 brettholcomb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ba583fdd05060112135019f7a9@mail.gmail.com \
--to=timo.horstschaefer@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox