Dnia 2015-08-22, o godz. 22:17:05
Philip Webb napisał(a):
> 150815 Holger Hoffstätte wrote:
> > On Sat, 15 Aug 2015 15:29:21 -0400, Joshua Kinard wrote:
> >> I've been super-busy as of late and just recently ran 'emerge --sync'
> >> on my main dev box for the first time after the git migration.
>
# Matt Turner (22 Aug 2015)
# nouveau has been in the kernel since 2.6.33
# Masked for removal in 30 days.
x11-base/nouveau-drm
150815 Holger Hoffstätte wrote:
> On Sat, 15 Aug 2015 15:29:21 -0400, Joshua Kinard wrote:
>> I've been super-busy as of late and just recently ran 'emerge --sync'
>> on my main dev box for the first time after the git migration.
>> I just synced my main dev box again, ~10 hours after the last sync
On Sat, Aug 22, 2015 at 4:47 PM, hasufell wrote:
> So my point stands. Games require their own set of policies (and ebuild
> writing guidelines).
I think we're somewhat talking past each other. I'm not debating that
it may be beneficial for games to have some specific policies, and
those should
On 08/22/2015 08:01 PM, Daniel Campbell (zlg) wrote:
>> The primary concern of gamers is that the game runs and that they
>> can reasonably install it (see the games-roguelike/nethack bug
>> which was unsolved for 8 years).
>
> What happened with that bug? 8 years? That's insane!
>
It got fixed
On 08/22/2015 05:25 PM, Rich Freeman wrote:
> On Saturday, August 22, 2015, hasufell wrote:
>>
>>
>> Games differ in a lot of ways and they _require_ different policies. In
>> some cases this also means more lax policies and in some cases more
>> strict policies.
>>
>> An example is unbundling lib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/22/2015 04:10 AM, hasufell wrote:
> On 08/22/2015 09:33 AM, Daniel Campbell (zlg) wrote:
>> On 08/21/2015 02:09 PM, James Le Cuirot wrote:
>>> On Fri, 21 Aug 2015 12:42:07 -0700 "Daniel Campbell (zlg)"
>>> wrote:
>>
> Sure, we did drop t
On Saturday, August 22, 2015, hasufell wrote:
>
>
> Games differ in a lot of ways and they _require_ different policies. In
> some cases this also means more lax policies and in some cases more
> strict policies.
>
> An example is unbundling libraries. While unbundling libraries is often
> a good
On Sat, 22 Aug 2015 13:10:54 +0200
hasufell wrote:
Great response, thanks!
> Because of that, I provide a 'bundled-libs' USE flag for almost all
> proprietary games I package (e.g. those from GOG). So in case
> something breaks, the user can still opt-out of all this.
I like unbundling but I al
On 08/22/2015 09:33 AM, Daniel Campbell (zlg) wrote:
> On 08/21/2015 02:09 PM, James Le Cuirot wrote:
>> On Fri, 21 Aug 2015 12:42:07 -0700 "Daniel Campbell (zlg)"
>> wrote:
>
Sure, we did drop this, but I don't really see this line of
argument actually accomplishing anything productiv
On Sat, Aug 22, 2015 at 3:33 AM, Daniel Campbell (zlg) wrote:
>
> Great question on the 'cdinstall' flag. Games from Humble Bundle and
> GOG are basically fetch-restricted and require the user to put the
> relevant distfile in /usr/portage/distfiles to install. 'cdinstall'
> could be applied only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/21/2015 02:09 PM, James Le Cuirot wrote:
> On Fri, 21 Aug 2015 12:42:07 -0700 "Daniel Campbell (zlg)"
> wrote:
>
>>> Sure, we did drop this, but I don't really see this line of
>>> argument actually accomplishing anything productive. Creati
12 matches
Mail list logo
