# @DEAD
# Ulrich Müller (2019-12-16)
# No longer used by any ebuild in the Gentoo repository.
# Removal in 30 days.
signature.asc
Description: PGP signature
# Almost all consumers gone, the remaining two are last-rited.
# Removal in 14 days.
git-2.eclass
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
# Michał Górny (2019-12-16)
# Old slot of unmaintained x11-libs/fox. Last touched in 2015, pending
# bump since. x11-misc/xfe is the only revdep.
# Removal in 30 days. Bug #703084.
x11-libs/fox:1.6
x11-misc/xfe
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally
On Sun, 2019-12-15 at 13:29 -0800, Zac Medico wrote:
> On 12/13/19 2:12 PM, Michael 'veremitz' Everitt wrote:
> > On 13/12/19 20:36, Michał Górny wrote [excerpted]:
> > > Is this really an argument for or *against* it? Developers are entirely
> > > capable of keeping seds that do nothing for
# Michał Górny (2019-12-16)
# All of FOX Toolkit packages are unmaintained. The library was last
# bumped in Jan 2016, and is pending bump since. Other packages are
# even more behind. Including media-sound/gogglesmm as the only revdep.
# Removal in 30 days. Bug #703088.
app-editors/adie
Il giorno lun 16 dic 2019 alle ore 13:39 Michał Górny
ha scritto:
>
>
> Comments
>
> WDYT?
>
> what about getting rid of RESTRICT="fetch" and manage everything inside
SRC_URI? Would that be technically feasible?
Ideally marking only the not re-distributable download and leaving
Hello, everyone.
I'd like to start a series of mails dedicated to features proposed for
including in EAPI 8. For a start, I'd like to discuss the topic of
selective fetch restriction [1]. It has been discussed at least in 2013
[2], and since it's finally got chance to be included, I think it's
> On Mon, 16 Dec 2019, Francesco Riosa wrote:
> what about getting rid of RESTRICT="fetch" and manage everything
> inside SRC_URI? Would that be technically feasible? Ideally marking
> only the not re-distributable download and leaving untouched the
> others
That would have the disadvantage
* Michael Orlitzky:
> I'm sure someone will object to the name acct-user/_milter-regex, but
> that would be the easiest option, being the upstream default.
Admittedly, _milter-regex makes me wince. It displeases my sense of
aesthetics and affects sorting order in acct-*. I'd like to lose the
> On Mon, 16 Dec 2019, Michał Górny wrote:
> Proposed solution
> =
> The current proposal is based on extending the current URI syntax to
> permit excluding individual files from the restriction. The idea is to
> prepend 'fetch+' to protocol to undo fetch restriction, or to
On Mon, Dec 16, 2019 at 8:33 AM Ulrich Mueller wrote:
>
> > On Mon, 16 Dec 2019, Francesco Riosa wrote:
>
> > what about getting rid of RESTRICT="fetch" and manage everything
> > inside SRC_URI? Would that be technically feasible? Ideally marking
> > only the not re-distributable download and
Penny for your thoughts, guys: I am thinking about splitting the
video_cards_i965 condition in virtual/opencl so that NEO is pulled in by
video_cards_iris instead, and I wonder if there is anything I haven't
thought about.
The reason why I would like to do this is that there is clear
On 12/15/19 5:31 PM, Michael Orlitzky wrote:
Without more information, all I can say is that there's probably a
better way to do whatever these users are doing that doesn't involve
modifying a system user. But regardless, Michał's answer is the right
one if you decide that you do want to modify
13 matches
Mail list logo
