public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Conary
Date: Thu, 21 Oct 2004 11:52:16 +0200	[thread overview]
Message-ID: <20041021095216.GA12088@gentoo.org> (raw)
In-Reply-To: <200410211030.29408.pauldv@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]

On Thu, Oct 21, 2004 at 10:30:21AM +0200, Paul de Vrieze wrote:
> You might want to try dispatch-conf. It is superior to etc-update in many 
> aspects, and it comes with gentoolkit. Further there is normally no need 
> to update every night. While there is no problem with it, it will 
> increase the maintenance load unnecessarilly.

Actually it's part of Portage (at least until .51_rc9), but that's
nitpicking :)

> The thing is that portage's binary packages are far from perfect when 
> compared for example with rpm's. The problem is caused by the fact that 
> two seemingly similar binary packages can be different to the extend that 
> one will work on your system and the other not. As gentoo is mainly a 
> source distribution the effort required to make binaries "better" is 
> probably too big. Even then all kinds of binary problems are unavoidable 
> and the main cause of releases in all binary distributions, even debian. 
> With source one can mix and match, with binary releases one must ensure 
> that all dependencies are completely compatible with the versions that 
> existed when the package was built.

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

Just a complementary note.

Wkr,
      Sven Vermeulen

-- 
  Documentation & PR project leader

  The Gentoo Project   <<< http://www.gentoo.org >>>

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-10-21  9:52 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 [this message]
2004-10-21 11:46     ` Roman Gaufman
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=20041021095216.GA12088@gentoo.org \
    --to=swift@gentoo.org \
    --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