public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: Ulrich Mueller <ulm@gentoo.org>,
	"Andreas K. Huettel" <dilfridge@gentoo.org>
Subject: Re: [gentoo-project] Re: [gentoo-dev-announce] Call for Council Agenda Items - 14 Oct 2014
Date: Mon, 13 Oct 2014 14:09:00 -0400	[thread overview]
Message-ID: <CAGfcS_=amWEOccnCvtrS912NMMQy1LwDo9n2=S7D9qPuBPY17Q@mail.gmail.com> (raw)
In-Reply-To: <20141013145952.293a60cf@pomiot.lan>

On Mon, Oct 13, 2014 at 8:59 AM, Michał Górny <mgorny@gentoo.org> wrote:
> Dnia 2014-10-13, o godz. 14:54:56
> Ulrich Mueller <ulm@gentoo.org> napisał(a):
>
>> >>>>> On Mon, 13 Oct 2014, Michał Górny wrote:
>>
>> > 2. Dependency updates [2] are stuck midway games. With no help from
>> > games team, the fact that most of the current dependencies don't
>> > make sense and that most of the games are proprietary, you shouldn't
>> > expect much sane progress anytime soon. Likely we're just going to
>> > end up updating the current dependencies knowing they're likely
>> > wrong.
>>
>> "Il meglio è l'inimico del bene." -- Voltaire
>>
>> You could start with the dependencies currently in ebuilds, and in
>> addition use tools like scanelf or lddtree for scanning the binaries
>> installed by the package. (Or even the old tools for porting packages
>> to modular X [4] could be used; it's a very similar task.)
>
> Proprietary games == no binaries for me.

My thought is that we should do what we can with what we have, give
notice to the maintainers, and pull the plugs on the emul packages (or
at least stop maintaining them, pulling them if they have security
issues).

I think the fact that we can have non-redistributable or even
proprietary software in portage is actually one of Gentoo's strengths.
However, it still needs to be maintained.  We can better tolerate
inactive maintainers for FOSS since anybody can step in and maintain
them.

If a proprietary package breaks, then it should be treecleaned.  I
don't think we have to tiptoe around them to keep this from happening.
They need to be maintained like any other package.


  reply	other threads:[~2014-10-13 18:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGfcS_m5cWLG_94-KMqaGef5JU-zr8-oJzjd4Q8QSAk=34QeeQ@mail.gmail.com>
2014-10-01  8:43 ` [gentoo-project] Re: [gentoo-dev-announce] Call for Council Agenda Items - 14 Oct 2014 Ulrich Mueller
2014-10-01 17:30 ` [gentoo-project] " Rich Freeman
2014-10-02 23:06   ` Michał Górny
2014-10-03 20:23 ` [gentoo-project] Re: [gentoo-dev-announce] " Andreas K. Huettel
2014-10-03 22:41   ` Rich Freeman
2014-10-04 12:30     ` Andreas K. Huettel
2014-10-04 15:04       ` Michał Górny
2014-10-13  9:04   ` Michał Górny
2014-10-13  9:59     ` Pacho Ramos
2014-10-13 10:06       ` Michał Górny
2014-10-13 10:18         ` Pacho Ramos
2014-10-13 12:54     ` Ulrich Mueller
2014-10-13 12:59       ` Michał Górny
2014-10-13 18:09         ` Rich Freeman [this message]
2014-10-13 14:44       ` Ciaran McCreesh

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='CAGfcS_=amWEOccnCvtrS912NMMQy1LwDo9n2=S7D9qPuBPY17Q@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=dilfridge@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=ulm@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