Ruud Koolen wrote:
>
> As a compromise solution for minor archs, it would be nice if there were a
> portage feature allowing me to ACCEPT_KEYWORDS those packages that are
> keyworded both ~arch, and stable on some major arch. For example, on m68k, it
> would select packages that are keyworded ~m68
Sergey Popov wrote:
> As i said earlier, problem begins when we NEED to stabilize
> something to prevent breakages and arch teams are slow.
Isn't that simply a matter of assigning and respecting priority on
bugs properly?
//Peter
pgpNUTerDIRPI.pgp
Description: PGP signature
On Thu, Jan 16, 2014 at 10:54 AM, Peter Stuge wrote:
> Sergey Popov wrote:
>> As i said earlier, problem begins when we NEED to stabilize
>> something to prevent breakages and arch teams are slow.
>
> Isn't that simply a matter of assigning and respecting priority on
> bugs properly?
Are you sugg
On 16/01/2014 19:56, Rich Freeman wrote:
> On Thu, Jan 16, 2014 at 10:54 AM, Peter Stuge wrote:
>> Sergey Popov wrote:
>>> As i said earlier, problem begins when we NEED to stabilize
>>> something to prevent breakages and arch teams are slow.
>>
>> Isn't that simply a matter of assigning and respe
Rich Freeman wrote:
> >> As i said earlier, problem begins when we NEED to stabilize
> >> something to prevent breakages and arch teams are slow.
> >
> > Isn't that simply a matter of assigning and respecting priority on
> > bugs properly?
>
> Are you suggesting that we should forbid people from w
Alan McKinnon wrote:
> "Respecting bug priority" feels like that corporate BS I have to put up
> with every day.
Gentoo is incorporated so maybe that fits. ;)
On a more serious note, please try to understand what I meant rather
than just what I wrote.
I wrote both "assigning" and "respecting"; y
On Thu, Jan 16, 2014 at 1:11 PM, Peter Stuge wrote:
> I certainly don't think the work needs to go away if the work is
> considered to be important. It's fine to have open bugs for years
> in the absence of a good solution.
I get what you're saying, though there is still a cost to leaving the
bug
On Thu, Jan 16, 2014 at 01:42:41PM -0500, Rich Freeman wrote:
> On Thu, Jan 16, 2014 at 1:11 PM, Peter Stuge wrote:
> > I certainly don't think the work needs to go away if the work is
> > considered to be important. It's fine to have open bugs for years
> > in the absence of a good solution.
>
>
Rich Freeman wrote:
> I get what you're saying, though there is still a cost to leaving the
> bug open to years. In this case it means an old package stays in the
> tree marked as stable. That either costs maintainers the effort to
> keep it work, or they don't bother to keep in working in which
On 16/01/2014 20:26, Peter Stuge wrote:
> Alan McKinnon wrote:
>> "Respecting bug priority" feels like that corporate BS I have to put up
>> with every day.
>
> Gentoo is incorporated so maybe that fits. ;)
>
> On a more serious note, please try to understand what I meant rather
> than just what
Alan McKinnon wrote:
> > I wrote both "assigning" and "respecting"
>
> I reckon the cardinal rule is "avoid as much as possible having priority
> set by someone who is not solving the problem". I think that comes close
> in my words to what you are saying.
Yes that's exactly what I mean. Thanks f
On Wed, 15 Jan 2014 23:28:04 -0800
Christopher Head wrote:
> If I need or want a feature or bugfix which isn’t in the newer
> version, I always have the choice to use ~.
Yes.
> If I don’t, why do I care if the package is a year old? I lose none
> of my time to use the old version, since it does
On Thu, 16 Jan 2014 10:20:37 +0400
Sergey Popov wrote:
> It can not go to no result, unless we have no breakages in stable,
> stable REMAINS stable. If it contains old, but working software - then
> it is stable.
An ebuild promoted to stable is because an arch team (or a privileged
maintainer to
On Thu, 16 Jan 2014, Sergey Popov wrote:
3. Also, another interesting question has come up in this thread, that of
non-binary packages. Should we give maintainers the option of
stabilizing them on all arch's themselves?
3. If code is interpreted rather then compiled, it does not matter that
it i
Sorry for following up myself,
On Fri, 17 Jan 2014, gro...@gentoo.org wrote:
OK, let's be conservative. Python and Perl scripts may break on some arches
(I'd say it's a rare exception, perhaps 1%, but still). But what about
dev-java/java-sdk-docs
dev-db/postgresql-docs
sys-kernel/linux-docs
de
On Thu, Jan 16, 2014 at 11:02 PM, wrote:
> Sorry for following up myself,
>
>
> On Fri, 17 Jan 2014, gro...@gentoo.org wrote:
>>
>> OK, let's be conservative. Python and Perl scripts may break on some
>> arches (I'd say it's a rare exception, perhaps 1%, but still). But what
>> about
>>
>> dev-ja
16 matches
Mail list logo
