From: Jason Cooper <gentoo@lakedaemon.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo as a development platform
Date: Sat, 16 Apr 2005 20:48:38 -0400 [thread overview]
Message-ID: <20050417004838.GN16840@lakedaemon.net> (raw)
In-Reply-To: <4261A173.3070008@gentoo.org>
Daniel Drake (dsd@gentoo.org) scribbled:
> Quite often, I use Gentoo's from-source nature to my advantage when developing
> or testing software packages.
>
> Gentoo is fairly well oriented for this kind of environment, but it's not
> brilliant. As an example, foo-3.2.1 (the latest version) is installed on my
> system, but more recently, they fixed a critical bug in the upstream CVS tree
> which I'd like to test the fix for. It's not dead simple for me to do this - I
> want to use the CVS sources with the ebuild already in portage. I have to use
> "ebuild foo-3.2.1.ebuild unpack" to extract the sources, then manually replace
> them with my CVS checkout. Or checkout CVS, make a new tarball, call it
> foo-3.2.1.tar.bz2, redigest and remerge the ebuild. Or I could create a
> foo-cvs ebuild and go to the trouble of making it mirror the contents of
> foo-3.2.1.ebuild exactly.
>
> It's great that its *possible* right now thanks to portage and co, but I'm
> interested in ways of making this easier. Before I give this more thought, I'd
> be interested to know if anyone has already got any scripts or tips :)
What about something akin to gcc? ie. you create a
/usr/local/portage/foo-ness/foo/foo-cvs.ebuild, then adapt gcc-config to
select which installed package to use, foo-1.2.3 or foo-cvs? Would
definitely be some work, but would be a good long-term, easily
maintainable solution. 'foo-config cvs' would use the last cvs build
you did, then 'foo-config 1.2.3' would drop you back to regular.
hth,
Cooper.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-17 0:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 23:36 [gentoo-dev] Gentoo as a development platform Daniel Drake
2005-04-16 23:43 ` Francesco Riosa
2005-04-17 0:07 ` Daniel Drake
2005-04-17 0:13 ` Robert Paskowitz
2005-04-17 1:03 ` Daniel Drake
2005-04-17 16:24 ` Malte S. Stretz
2005-04-19 19:35 ` Paul de Vrieze
2005-04-16 23:43 ` Brian Harring
2005-04-17 0:03 ` Daniel Drake
2005-04-17 1:39 ` Donnie Berkholz
2005-04-17 2:26 ` Brian Harring
2005-04-17 0:48 ` Jason Cooper [this message]
2005-04-17 1:14 ` Brian Harring
2005-04-17 1:38 ` Donnie Berkholz
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=20050417004838.GN16840@lakedaemon.net \
--to=gentoo@lakedaemon.net \
--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