From: Roman Gaufman <hackeron@gmail.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Conary
Date: Thu, 21 Oct 2004 11:46:14 +0000 [thread overview]
Message-ID: <921ad39e04102104464437f153@mail.gmail.com> (raw)
In-Reply-To: <20041021095216.GA12088@gentoo.org>
On Thu, 21 Oct 2004 11:52:16 +0200, Sven Vermeulen <swift@gentoo.org> wrote:
> Actually it's part of Portage (at least until .51_rc9), but that's
> nitpicking :)
yup:
server / # qpkg -f /usr/sbin/dispatch-conf
sys-apps/portage *
What do you mean until .51_rc9? -- will it be included in .51?
There's no way in hell I'm moving back to etc-update -- and frankly, I
dont see how anyone can tolerate it :)
> Some issues with binary releases are covered by a document that rac has on
> his dev page. It's not the official Gentoo policy, but it does make you
> think about it :)
>
> http://dev.gentoo.org/~rac/binaries.html
Personally, I find binary packages on gentoo perfect for my use. I
have several computers on the network, all running gentoo with no gcc
or any header files. I then have an offline machine that gets
everything compiled and put on a shared /usr/portage for all the
machines to just emerge -k simultaneously.
That way when I emerge something, I can review the config files, add
some custom options and some fancy polish and quickpkg will bundle
everything together all pre-configured.
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-10-21 11:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 22:02 [gentoo-portage-dev] Conary andrea ferraris
2004-10-21 8:30 ` Paul de Vrieze
2004-10-21 9:52 ` Sven Vermeulen
2004-10-21 11:46 ` Roman Gaufman [this message]
2004-10-21 12:44 ` Sven Vermeulen
2004-10-21 13:20 ` Roman Gaufman
2004-10-21 13:52 ` Jason Stubbs
2004-10-24 17:44 ` andrea ferraris
2004-10-24 21:47 ` Roman Gaufman
2004-10-25 21:06 ` andrea ferraris
2004-10-21 19:00 ` Nathaniel McCallum
2004-10-21 19:19 ` Luke-Jr
2004-10-22 8:07 ` Paul de Vrieze
2004-10-22 11:24 ` Jason Stubbs
2004-10-22 13:11 ` John Nilsson
2004-10-22 13:21 ` Jason Stubbs
2004-10-22 13:31 ` Paul de Vrieze
2004-10-22 19:33 ` John Nilsson
2004-10-24 3:18 ` Ed Grimm
2004-10-24 9:15 ` Paul de Vrieze
2004-10-24 11:27 ` andrea ferraris
2004-10-24 20:52 ` Paul de Vrieze
2004-10-24 9:33 ` Sven Vermeulen
2004-10-24 11:28 ` andrea ferraris
2004-10-25 18:47 ` [gentoo-portage-dev] Conary - dispatch-conf LinuxGuy
2004-10-28 2:55 ` Ed Grimm
2004-10-28 17:18 ` LinuxGuy
2004-11-12 9:23 ` Ed Grimm
2004-11-28 20:15 ` LinuxGuy
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=921ad39e04102104464437f153@mail.gmail.com \
--to=hackeron@gmail.com \
--cc=gentoo-portage-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