On 03/26/2018 09:26 PM, Rich Freeman wrote:
> On Mon, Mar 26, 2018 at 9:19 PM, kuzetsa wrote:
>> On 03/20/2018 08:08 PM, Rich Freeman wrote:
>>
>>>
>>> Actually, I think it is more of a technical constraint. It is
>>> basically impossible to blacklist somebody on a mailing list, since
>>> all the
On Mon, Mar 26, 2018 at 9:19 PM, kuzetsa wrote:
> On 03/20/2018 08:08 PM, Rich Freeman wrote:
>
>>
>> Actually, I think it is more of a technical constraint. It is
>> basically impossible to blacklist somebody on a mailing list, since
>> all they need to do is roll up a new email address.
>>
>> I
On 03/20/2018 08:08 PM, Rich Freeman wrote:
> On Tue, Mar 20, 2018 at 7:54 PM, Benda Xu wrote:
>> William Hubbs writes:
>>
>>> I do feel that this decision reflects badly on us as a community and
>>> should be reversed immediately. The proper way to deal with people who
>>> have bad behavior is t
On Mon, Mar 26, 2018 at 11:58:00PM +0200, Michał Górny wrote:
> W dniu pon, 26.03.2018 o godzinie 16∶33 -0500, użytkownik Marty E.
> Plummer napisał:
> > As a pretty simple eclass, which only inherited multilib in
> > order to get $(get_libdir) and eutils for who knows why, and
> > all its consumer
W dniu pon, 26.03.2018 o godzinie 16∶33 -0500, użytkownik Marty E.
Plummer napisał:
> As a pretty simple eclass, which only inherited multilib in
> order to get $(get_libdir) and eutils for who knows why, and
> all its consumers bumped to EAPI=6, it makes sense to require
> EAPI 6 for this eclass
>
As a pretty simple eclass, which only inherited multilib in
order to get $(get_libdir) and eutils for who knows why, and
all its consumers bumped to EAPI=6, it makes sense to require
EAPI 6 for this eclass
Package-Manager: Portage-2.3.24, Repoman-2.3.6
---
eclass/freedict.eclass | 7 +--
1 fi
On Sun, Mar 18, 2018 at 9:39 AM, Alec Warner wrote:
>
>
> On Sun, Mar 18, 2018 at 8:49 AM, Pacho Ramos wrote:
>
>> # Pacho Ramos (18 Mar 2018)
>> # Unresolved security issues (#606652), tests fail (#628622, #337249).
>> # Removal in a month.
>> net-dns/hesiod
>>
>> # Pacho Ramos (18 Mar 2018)
On Mon, 26 Mar 2018 20:07:07 +0200
Jonas Stein wrote:
> > [...]
> >> This is not a very nice solution, but it works so far. One
> >> difficulty is, that there is no 1:1 relation between the texlive
> >> distribution and dev-texlive/* at the moment.
> > There is a 1:1 relation.
>
> A full i
On 03/26/2018 09:48 AM, Thomas Deutschmann wrote:
> On 2018-03-23 18:44, Patrick McLean wrote:
>> At my (and zmedico's) employer we use Gentoo heavily (all of our servers
>> run it), and have a few large internal overlays and hundreds of internal
>> profiles. There are packages in upstream Gentoo t
Hi Alexis,
> The real reason is that we need to go through ~arch testing, fixing rev
> deps that might need update to their .tex files because the underlying
> packages they use has changed, adapt the deps for some potential
> changes, and then a stablereq round.
I agree. This makes the situatio
On 2018-03-22 09:57, Dirkjan Ochtman wrote:
> On the face of it, I wouldn't drop the "prometheus-" prefix if
> app-metrics is to be the home to other tools. Otherwise, other tools
> like graphite or collectd might want very similar names for the same
> tools out there.
I second this. Please keep
On 2018-03-23 18:44, Patrick McLean wrote:
> At my (and zmedico's) employer we use Gentoo heavily (all of our servers
> run it), and have a few large internal overlays and hundreds of internal
> profiles. There are packages in upstream Gentoo that we maintain an
> internal fork of, and it would be
On Mon, 26 Mar 2018 11:40:12 +0200
Jonas Stein wrote:
> Hi,
>
> I just read
> https://bugs.gentoo.org/625908#c5
> and saw that we do not have a good documentation on this and many
> packages in the tree ship with strange tex dependencies.
>
> I started a documentation on our wiki
> https://wik
On Mon, 26 Mar 2018 11:57:49 +0200
Jonas Stein wrote:
> An installation via tlmgr provides many updates per day, but
> our distributed TeXLive is unfortunately always behind.
> Typically TeXLive on gentoo is 6-12 months behind upstream, because we
> have to bump a lot manually.
That is not the re
Le lundi 26 mars 2018 à 13:55 +0200, Michał Górny a écrit :
> Dnia 26 marca 2018 10:47:04 CEST, Gilles Dartiguelongue rg> napisał(a):
> > Le lundi 26 février 2018 à 23:24 +0100, Michał Górny a écrit :
> > > 'luajit' is used consistently in 25+ packages. Make it a global
> > > flag.
> >
> > Not th
Dnia 26 marca 2018 10:47:04 CEST, Gilles Dartiguelongue
napisał(a):
>Le lundi 26 février 2018 à 23:24 +0100, Michał Górny a écrit :
>> 'luajit' is used consistently in 25+ packages. Make it a global flag.
>
>Not that I have a strong opinion about it, but wouldn't it be better to
>have USE="lua ji
Dear all,
there was a question on the tex@gentoo ml from a user, who needs a very
recent TeXLive in order to be compatible with other setups.
This is also very important, for users of the more recent programs like
lualatex. Many packages do not work properly in the unfixed old version.
An install
Hi,
I just read
https://bugs.gentoo.org/625908#c5
and saw that we do not have a good documentation on this and many
packages in the tree ship with strange tex dependencies.
I started a documentation on our wiki
https://wiki.gentoo.org/wiki/Notes_on_TeX_related_ebuilds
Please help to complete it
On Sun, Mar 4, 2018 at 12:37 PM, Michał Górny wrote:
> I think this cause the trouble of specifying '-r0' rather rarely, and it
> will decrease the number of mistakes, also effectively making Gentoo
> development easier. It is somewhat inspired by the handling of slot
> operators (where repoman e
Le dimanche 04 mars 2018 à 12:37 +0100, Michał Górny a écrit :
> Hi, everyone.
>
> I have proposed a new check for repoman [1] (with a patch at [2])
> that
> would warn developers about suspicious '=' deps.
>
> By suspicious, I mean dependencies '=foo-1.2.3' which are sometimes
> mistakenly used
Le lundi 26 février 2018 à 23:24 +0100, Michał Górny a écrit :
> 'luajit' is used consistently in 25+ packages. Make it a global flag.
Not that I have a strong opinion about it, but wouldn't it be better to
have USE="lua jit" like libpeas does ? Use flags aren't supposed to
match library names but
On 03/25/2018 02:02 AM, Kent Fredric wrote:
> On Sat, 24 Mar 2018 21:43:41 -0700
> Zac Medico wrote:
>
>> But if the majority demographic is as you describe, then they shouldn't
>> be using anything having dependencies that require package.unmask or **
>> keywords changes.
>
> Again, they *dont*
22 matches
Mail list logo
