public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2013-05-14
Date: Wed, 01 May 2013 10:27:27 -0700	[thread overview]
Message-ID: <5181507F.5060602@gentoo.org> (raw)
In-Reply-To: <20130501163556.6ab95917@googlemail.com>

On 05/01/2013 08:35 AM, Ciaran McCreesh wrote:
> On Wed, 1 May 2013 17:28:02 +0200
> Michał Górny <mgorny@gentoo.org> wrote:
>> On Wed, 1 May 2013 16:22:47 +0100
>> Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:
>>> On Wed, 01 May 2013 08:18:50 -0700
>>> Zac Medico <zmedico@gentoo.org> wrote:
>>>> I know that this feature has been questioned by some, especially
>>>> by people involved with Paludis (which doesn't implement
>>>> preserve-libs). I think that the main compliant is that
>>>> preserve-libs doesn't preserve any non-library dependencies (such
>>>> as configuration files) that a library may depend on.
>>>
>>> ...and that it's utterly frickin' broken as a concept, and that
>>> adopting it will slow down people switching to the proper solution
>>> to the problem, which is slots.
>>
>> Convince the developers to split packages into proper parts, then we
>> can talk. Or even better, convince upstreams to split their packages.
> 
> It's necessary, and the way to convince developers is to stop providing
> a nasty hack as a not-really-working alternative.

As downstream packagers, do we or can we really expect to have that much
influence of upstream developers? If the big binary distros are willing
to package these things without complaints, then how likely is it that
upstream developers will change their ways?
-- 
Thanks,
Zac


  reply	other threads:[~2013-05-01 17:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-27 16:59 [gentoo-project] Call for agenda items - Council meeting 2013-05-14 Petteri Räty
2013-04-27 21:27 ` Michał Górny
2013-05-01  7:37 ` Ulrich Mueller
2013-05-01 15:15 ` Mike Gilbert
2013-05-01 15:18 ` Zac Medico
2013-05-01 15:22   ` Ciaran McCreesh
2013-05-01 15:28     ` Michał Górny
2013-05-01 15:35       ` Ciaran McCreesh
2013-05-01 17:27         ` Zac Medico [this message]
2013-05-01 17:30           ` Ciaran McCreesh
2013-05-01 17:35             ` Rich Freeman
2013-05-01 17:45               ` Ciaran McCreesh
2013-05-01 16:35     ` Rich Freeman
2013-05-01 15:39 ` Michał Górny

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=5181507F.5060602@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-project@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