public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Gryniewicz <dang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] proxy-dev (an alternative to sunrise?)
Date: Sun, 30 Jul 2006 12:46:32 -0400	[thread overview]
Message-ID: <1154277992.8563.10.camel@athena.fprintf.net> (raw)
In-Reply-To: <200607301550.47668.pauldv@gentoo.org>

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

On Sun, 2006-07-30 at 15:50 +0200, Paul de Vrieze wrote:
> On Friday 28 July 2006 20:51, Donnie Berkholz wrote:
> > Robert Cernansky wrote:
> > > If I have some application that is not included in portage why
> > > I decide to make an ebuild? Because I hope that then it will be
> > > accepted and included to portage, so maintained by developers (big
> > > thanks for this). If I have to take care of package + ebuild +
> > > dependencies, I'll rather choose not to make an ebulid but compile
> > > package right from .tar.gz archive.
> >
> > Many people disagree with you here, that's why overlays exist. Somebody
> > wants to use Portage to manage ebuilds that aren't yet in the actual tree.
> 
> I'm one of those. Portage namely is also a package manager allowing what using 
> the tarbal method does not: file tracking and deinstallation.
> 
> Paul

FWIW, my company uses Gentoo and overlays extensively to manage our
workstations and testbeds.  The packages we have are not suitable for
inclusion in portage (for a number of reasons), and we have no intention
of ever submitting them.

Overlays are a *great* way of customizing a local network of boxes to be
different than upstream Gentoo for whatever reason.  I, personally, find
this to be a more useful function than a place to hold ebuilds not-yet
in portage (although, I do that also).

-- 
Daniel Gryniewicz
Gentoo AMD64 Team / Gentoo Gnome Herd / Gentoo Kernel Herd / Gentoo Printing Herd
AMD64 Operational AT Lead

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2006-07-30 16:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28  2:19 [gentoo-dev] proxy-dev (an alternative to sunrise?) Luis Francisco Araujo
2006-07-28  2:56 ` Thomas Cort
2006-07-28  3:56   ` Luis Francisco Araujo
2006-07-28  8:39 ` [gentoo-dev] " Stefan Schweizer
2006-07-28  9:44   ` Luis Francisco Araujo
2006-07-28 14:16     ` Luca Longinotti
2006-07-28 15:39     ` Enrico Weigelt
2006-07-28 17:23       ` Luis Francisco Araujo
2006-07-30 16:36       ` Simon Stelling
2006-07-28 18:02 ` [gentoo-dev] " Robert Cernansky
2006-07-28 18:26   ` Luis Francisco Araujo
2006-07-28 19:00     ` Robert Cernansky
2006-07-28 19:49       ` Alexandre Buisse
2006-07-28 20:09         ` Robert Cernansky
2006-07-28 21:35           ` Luis Medinas
2006-07-28 18:51   ` Donnie Berkholz
2006-07-28 19:07     ` Robert Cernansky
2006-07-28 19:26       ` Luis Francisco Araujo
2006-07-28 19:55         ` Robert Cernansky
2006-07-29  0:19     ` Alastair Tse
2006-07-29  9:29       ` Bruno
2006-07-29 22:36         ` Luis Francisco Araujo
2006-07-30 13:50     ` Paul de Vrieze
2006-07-30 16:46       ` Daniel Gryniewicz [this message]
2006-07-29 18:16 ` [gentoo-dev] " Ryan Hill
2006-07-29 22:49   ` Luis Francisco Araujo

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=1154277992.8563.10.camel@athena.fprintf.net \
    --to=dang@gentoo.org \
    --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