Le 03/05/2019 à 18:29, Eli Schwartz via aur-general a écrit :
> On 5/3/19 11:44 AM, Bruno Pagani wrote:
>> I still think that you would get a better user experience even for this
>> case by telling the users explicitely that this depends on llvm-git.
>> Because else, people would install mesa-git
On 5/3/19 11:44 AM, Bruno Pagani wrote:
> I still think that you would get a better user experience even for this
> case by telling the users explicitely that this depends on llvm-git.
> Because else, people would install mesa-git once, which will pull
> llvm-git as a dependency and build it for
Le 03/05/2019 à 17:32, Eli Schwartz a écrit :
> On 5/3/19 11:25 AM, Bruno Pagani wrote:
>> Yes, and he can solves that by *pinning a comment telling so*. ;)
> Pinning a comment telling people how to get the default expected User
> Experience in a non-default way, sucks.
Not “the default”. LW’s
On Fri, 3 May 2019 11:32:57 -0400
Eli Schwartz via aur-general wrote:
> On 5/3/19 11:25 AM, Bruno Pagani wrote:
> > Yes, and he can solves that by *pinning a comment telling so*. ;)
>
> Pinning a comment telling people how to get the default expected User
> Experience in a non-default way,
On 5/3/19 11:25 AM, Bruno Pagani wrote:
> Yes, and he can solves that by *pinning a comment telling so*. ;)
Pinning a comment telling people how to get the default expected User
Experience in a non-default way, sucks.
The package maintainer thinks that the average user will dislike the
resulting
Le 03/05/2019 à 17:14, Eli Schwartz via aur-general a écrit :
> On 5/3/19 10:23 AM, Bruno Pagani wrote:
>> Le 03/05/2019 à 16:04, Eli Schwartz via aur-general a écrit :
>>> Lone Wolf's point here, is that mesa-git results in different codegen
>>> and different features, if the build-time
On 5/3/19 10:23 AM, Bruno Pagani wrote:
> Le 03/05/2019 à 16:04, Eli Schwartz via aur-general a écrit :
>> Lone Wolf's point here, is that mesa-git results in different codegen
>> and different features, if the build-time compilation environment is
>> llvm-git.
>
> Yes, so say so in a pinned
On Fri, May 03, 2019 at 06:00:32PM +0300, Konstantin Gizdov wrote:
> I understand we have standards and requirements and suggestions and best
> practices and so on, but for the Arch User Repository - is Lone_Wolf not
> allowed to make a package called
>
On 03/05/2019 17:23, Bruno Pagani via aur-general wrote:
> Le 03/05/2019 à 16:04, Eli Schwartz via aur-general a écrit :
>
>> Furthermore, I defy the idea that even users building it themselves
>> constitute "user stupidity", because as Lone Wolf's explanation
>> *explicitly* called out, it is
Le 03/05/2019 à 16:04, Eli Schwartz via aur-general a écrit :
> On 5/1/19 10:53 AM, Doug Newgard via aur-general wrote:
>> On Wed, 1 May 2019 12:38:41 +0200
>> Lone_Wolf wrote:
>>> Assumptions :
>>>
>>> mesa-git depends on llvm and llvm-libs
>>>
>>> AUR only has one mesa-git package
>>>
>>> User
On Fri, 3 May 2019 10:04:39 -0400
Eli Schwartz via aur-general wrote:
> On 5/1/19 10:53 AM, Doug Newgard via aur-general wrote:
> > On Wed, 1 May 2019 12:38:41 +0200
> > Lone_Wolf wrote:
> >> Assumptions :
> >>
> >> mesa-git depends on llvm and llvm-libs
> >>
> >> AUR only has one mesa-git
On 5/1/19 10:53 AM, Doug Newgard via aur-general wrote:
> On Wed, 1 May 2019 12:38:41 +0200
> Lone_Wolf wrote:
>> Assumptions :
>>
>> mesa-git depends on llvm and llvm-libs
>>
>> AUR only has one mesa-git package
>>
>> User builds in clean chroot with devtools
>>
>> User wants mesa feature X,
Hi,
Due to irreconcilable differences wrt mesa trunk packaging, I am
stepping down as the maintainer of those packages.
I hope someone will volunteer to take over these packages and there will
be a smooth transition.
The packages will keep depending on llvm trunk until I transfer
13 matches
Mail list logo
