public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] "Commercial" software in portage
Date: Fri, 23 Sep 2005 10:59:28 -0400	[thread overview]
Message-ID: <1127487568.24269.157.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <200509232308.10865.jstubbs@gentoo.org>

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

On Fri, 2005-09-23 at 23:08 +0900, Jason Stubbs wrote:
> *Relax!* ;)

I'm quite calm, actually.

> I meant extending the fetch-restriction concept to include all cases where 
> an ebuild is not fully self-contained; that is, cases where the ebuild is 
> not capable of obtaining all necessary components to get a package to a 
> fully-functional state.

That would be fine.  I'm not sure how extending fetch restriction would
do it, but I'm also not a portage developer.

> Deferring discussion about it.. well, it scares me to be completely honest. 
> It becomes another one of those "is this going to change the requirements?" 
> that's always lurking.

I personally don't see it as a big enough issue to sweat it.  If it
doesn't make it into the next portage version, we shoot for one after
that.

> > I think I was looking for something where a user could tell before they 
> > even decided to merge the package, via emerge -S or packages.gentoo.org, 
> > or preferably both.
> 
> Is that the only requirement? Just a boolean attribute that says the user 
> will have to pay money in order to make use of the package? If so, it would 
> seem that metadata.xml would be the perfect place, but I'll think on that 
> and come back to it.

That is the only requirement that *I* had based on discussion with a
couple users.  They just wanted to know ahead of time that a package
they were looking at wouldn't work without them buying it.

> > > So, if RESTRICT="fetch" were to be overloaded, there is the issue of
> > > both fetch-restricted and non-fetch-restricted downloads in the one
> > > package. I would think this issue exists already for some packages. How
> > > is it dealt with at the moment?
> >
> > Currently, we just restrict the whole thing, as we have no other choice.
> > On some packages, it sucks pretty badly if there's only a single
> > restricted tarball and many unrestricted tarballs.
> 
> Perhaps leave this one for another time? :)

Agreed.  This is best left for later.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
Games - Developer
Gentoo Linux

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

  reply	other threads:[~2005-09-23 15:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-21 17:31 [gentoo-dev] "Commercial" software in portage Matthew Marlowe
2005-09-21 17:54 ` José Carlos Cruz Costa
2005-09-21 18:00   ` Daniel Ostrow
2005-09-21 18:15     ` Chris Gianelloni
2005-09-22  8:26     ` Philippe Trottier
2005-09-23 14:42       ` Brian Harring
2005-09-23 15:06         ` Jason Stubbs
2005-09-21 18:08   ` Daniel Ostrow
2005-09-21 18:13   ` Chris Gianelloni
2005-09-21 17:57 ` Chris Gianelloni
2005-09-21 22:55   ` Lance Albertson
2005-09-22 13:30     ` Chris Gianelloni
2005-09-22 16:46       ` Brian Harring
2005-09-22 17:30         ` Chris Gianelloni
2005-09-22 20:29           ` Brian Harring
2005-09-22 21:09             ` Chris Gianelloni
2005-09-22 21:57               ` warnera6
2005-09-22 22:01                 ` Ciaran McCreesh
2005-09-23 13:09                   ` Chris Gianelloni
2005-09-23  1:38               ` Jason Stubbs
2005-09-23 13:28                 ` Chris Gianelloni
2005-09-23 14:08                   ` Jason Stubbs
2005-09-23 14:59                     ` Chris Gianelloni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-21 13:51 Chris Gianelloni
2005-09-21 20:15 ` Paweł Madej
2005-09-21 22:31 ` Marius Mauch
2005-09-22  8:14   ` Thierry Carrez
2005-09-22 13:34     ` Chris Gianelloni
2005-09-22 13:28   ` Chris Gianelloni
2005-09-22 15:37     ` Georgi Georgiev
2005-09-22 15:54       ` Chris Gianelloni
2005-09-22 16:56         ` Cory Visi
2005-09-22 17:13           ` Matti Bickel
2005-09-22 17:04         ` 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=1127487568.24269.157.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@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