W dniu nie, 12.11.2017 o godzinie 21∶22 -0500, użytkownik Joshua Kinard
napisał:
> On 10/24/2017 00:11, Michał Górny wrote:
> > W dniu wto, 24.10.2017 o godzinie 06∶04 +0200, użytkownik Michał Górny
> > napisał:
>
> [snip]
>
> > > > [BOBO06] is relevant research here, I cited it in the work that
On 11/12/2017 22:48, Gordon Pettey wrote:
> On Sun, Nov 12, 2017 at 8:22 PM, Joshua Kinard wrote:
>
>> Minor clarification, old single core //and// uni-processor. Some older
>> machines have multiple physical CPUs that are single-core. Threading
>> should be
>> okay on these, as long as the thr
On Sun, Nov 12, 2017 at 8:22 PM, Joshua Kinard wrote:
> Minor clarification, old single core //and// uni-processor. Some older
> machines have multiple physical CPUs that are single-core. Threading
> should be
> okay on these, as long as the thread count stays under NR_CPUS.
>
> I also have a r
On 19/06/17 15:20, Michał Górny wrote:
> The GNOME team has committed the xdg-utils.eclass serving exactly
> the same purpose as fdo-mime.eclass, supposedly with the goal of
> replacing it. However, it seems that they have never bothered to
> actually hint the deprecation in the fdo-mime.eclass in
On 10/24/2017 00:11, Michał Górny wrote:
> W dniu wto, 24.10.2017 o godzinie 06∶04 +0200, użytkownik Michał Górny
> napisał:
[snip]
>>> [BOBO06] is relevant research here, I cited it in the work that went into
>>> GLEP59, the last time we updated the hashes. The less-technical explanation
>>> of
/stm32flash 20171107-12:26 jer 78a851d9ce5
dev-lang/sassc 20171107-08:26 tetromino 28bf57bb04b
dev-libs/libsass20171107-08:25 tetromino fceed9619b8
dev-python/pilkit 20171112-13:31 jstein592f68ce76d
dev-python/pyghmi 20171107-02:47 zmedico
Am Sonntag, 12. November 2017, 20:53:15 CET schrieb Joshua Kinard:
>
> I take it Python was fixed to handle this?
>
Yes, newest ~arch in all python slots is fixed.
(That was the main blocker for keywording.)
--
Andreas K. Hüttel
dilfri...@gentoo.org
Gentoo Linux developer (council, perl, libr
On 11/11/2017 11:49, Andreas K. Huettel wrote:
> Hi all,
>
> in the next days I'll likely re-add keywords to glibc-2.26. So, if you
> haven't
> fixed your package for build failures yet, now would be the time.
>
> The tracker is https://bugs.gentoo.org/show_bug.cgi?id=glibc-2.26 with
> appro
> On Sun, 12 Nov 2017, Michael Orlitzky wrote:
> Some day -- I'll add it to my list. For now I'll update the docs to
> explain why you should use keepdir, and do a QA warning for empty
> directories. Then how does this sound for EAPI=next?
> * Ban keepdir.
> * Have portage call its keepd
Am Samstag, 11. November 2017, 17:49:37 CET schrieb Andreas K. Huettel:
> Hi all,
>
> in the next days I'll likely re-add keywords to glibc-2.26. So, if you
> haven't fixed your package for build failures yet, now would be the time.
>
And done.
>
> The tracker is https://bugs.gentoo.org/show_bu
W dniu nie, 12.11.2017 o godzinie 07∶53 -0500, użytkownik Michael
Orlitzky napisał:
> On 11/11/2017 02:26 PM, Michał Górny wrote:
> > >
> > > As far as the actual implementation goes, I'm not sure that
> > > automatically-generated ".keep" files are better than having the package
> > > manager mai
On 11/11/2017 02:26 PM, Michał Górny wrote:
>>
>> As far as the actual implementation goes, I'm not sure that
>> automatically-generated ".keep" files are better than having the package
>> manager maintain its own database. The latter would be more complex, but
>> would avoid littering everyone's f
12 matches
Mail list logo
