Hello Drew,
I am a fan of your work on Sway and wlroots, but some of your statements left
me pretty disappointed.
>For the AUR I don't keep up with upstream releases, I just wait for
>someone to mark the package as outdated. For Alpine Linux I use a
>combination of subscribing to the upstream
On Thu, Feb 28, 2019 at 12:51 PM Josef Miegl wrote:
> Although I don't have high expectations when dealing with AUR packages, it is
> absolutely the maintainers job to keep track of upstream updates. This
> mindset is probably the reason why there is so much out of date stuff on the
> AUR. It
On 2/28/19 2:58 PM, Jerome Leclanche wrote:
> On Thu, Feb 28, 2019 at 12:51 PM Josef Miegl wrote:
>> Although I don't have high expectations when dealing with AUR packages, it
>> is absolutely the maintainers job to keep track of upstream updates. This
>> mindset is probably the reason why
Am 28.02.2019 um 04:25 schrieb Drew DeVault via aur-general:
On 2019-02-28 2:22 AM, Levente Polyak via aur-general wrote:
For the AUR I don't keep up with upstream releases, I just wait for
someone to mark the package as outdated. For Alpine Linux I use a
combination of subscribing to the
> From: Drew DeVault via aur-general
> Sent: Thu Feb 28 04:25:10 CET 2019
> To: Discussion about the Arch User Repository (AUR)
>
> Cc: Drew DeVault
> Subject: Re: [aur-general] Trusted user application: Drew DeVault
>
>
> On 2019-02-28 2:22 AM, Levente Polyak via aur-general wrote:
> > >
On February 28, 2019 8:58:06 AM EST, Jerome Leclanche wrote:
>OT: We should maybe have the AUR lint PKGBUILDs on git push (and
>reject really bad ones) if we want to improve that situation.
>
>J. Leclanche
I've been thinking enforcing the use of makechrootpkg and namcap on package
submission
On 2/28/19 11:22 AM, Daniel M. Capella via aur-general wrote:
> On February 28, 2019 8:58:06 AM EST, Jerome Leclanche
> wrote:
>
>
>
>> OT: We should maybe have the AUR lint PKGBUILDs on git push (and
>> reject really bad ones) if we want to improve that situation.
>>
>> J. Leclanche
>
>
On February 28, 2019 11:33:36 AM EST, "brent s." wrote:
>On 2/28/19 11:22 AM, Daniel M. Capella via aur-general wrote:
>> On February 28, 2019 8:58:06 AM EST, Jerome Leclanche
> wrote:
>>
>>
>>
>>> OT: We should maybe have the AUR lint PKGBUILDs on git push (and
>>> reject really bad ones) if
Am 28.02.2019 um 17:34 schrieb Jerome Leclanche:
On Thu, Feb 28, 2019 at 5:22 PM Daniel M. Capella via aur-general
wrote:
On February 28, 2019 8:58:06 AM EST, Jerome Leclanche wrote:
OT: We should maybe have the AUR lint PKGBUILDs on git push (and
reject really bad ones) if we want to
On 2/28/19 11:22 AM, Daniel M. Capella via aur-general wrote:
> On February 28, 2019 8:58:06 AM EST, Jerome Leclanche
> wrote:
>
>
>
>> OT: We should maybe have the AUR lint PKGBUILDs on git push (and
>> reject really bad ones) if we want to improve that situation.
>>
>> J. Leclanche
>
>
On 2/28/19 9:26 AM, Levente Polyak via aur-general wrote:
> On 2/28/19 2:58 PM, Jerome Leclanche wrote:
>> On Thu, Feb 28, 2019 at 12:51 PM Josef Miegl wrote:
>>> Although I don't have high expectations when dealing with AUR packages, it
>>> is absolutely the maintainers job to keep track of
On 2/28/19 3:33 PM, Jerome Leclanche wrote:
>
> We have TUs with hundreds of packages. Beyond automatic checks, do you
> really expect they keep up with every single release?
> I've myself updated several packages that were out of date (and
> unflagged) in [community]. I'm not saying the attitude
On Thu, Feb 28, 2019 at 02:58:06PM +0100, Jerome Leclanche wrote:
> No, it is not, and please don't expect this of volunteers.
Right, I don't expect that from AUR volunteers, but that doesn't mean the AUR
shouldn't be taken seriously. If the maitainer has not interest in updating
and seeking out
On 2/28/19 8:58 AM, Jerome Leclanche wrote:
> On Thu, Feb 28, 2019 at 12:51 PM Josef Miegl wrote:
>> Although I don't have high expectations when dealing with AUR packages, it
>> is absolutely the maintainers job to keep track of upstream updates. This
>> mindset is probably the reason why
On Thu, Feb 28, 2019 at 3:26 PM Levente Polyak via aur-general
wrote:
>
> On 2/28/19 2:58 PM, Jerome Leclanche wrote:
> > On Thu, Feb 28, 2019 at 12:51 PM Josef Miegl wrote:
> >> Although I don't have high expectations when dealing with AUR packages, it
> >> is absolutely the maintainers job to
On 2/28/19 3:43 PM, Jerome Leclanche wrote:
> On Thu, Feb 28, 2019 at 3:36 PM Levente Polyak via aur-general
> wrote:
>>
>> On 2/28/19 3:33 PM, Jerome Leclanche wrote:
>>>
>>> We have TUs with hundreds of packages. Beyond automatic checks, do you
>>> really expect they keep up with every single
On February 28, 2019 11:34:08 AM EST, Jerome Leclanche wrote:
>On Thu, Feb 28, 2019 at 5:22 PM Daniel M. Capella via aur-general
> wrote:
>>
>> On February 28, 2019 8:58:06 AM EST, Jerome Leclanche
> wrote:
>>
>>
>>
>> >OT: We should maybe have the AUR lint PKGBUILDs on git push (and
>> >reject
On Thu, Feb 28, 2019 at 3:36 PM Levente Polyak via aur-general
wrote:
>
> On 2/28/19 3:33 PM, Jerome Leclanche wrote:
> >
> > We have TUs with hundreds of packages. Beyond automatic checks, do you
> > really expect they keep up with every single release?
> > I've myself updated several packages
The AUR is not community. The expectations are higher for trusted users
- hence the trust. Naturally responding to emails, keeping up with new
releases, etc, is part of the role. That's why it's a *role* - it serves
to define the responsibilities. There is no role for AUR package
maintainer
On 2/28/19 4:49 PM, Drew DeVault via aur-general wrote:
> The AUR is not community. The expectations are higher for trusted users
> - hence the trust. Naturally responding to emails, keeping up with new
> releases, etc, is part of the role. That's why it's a *role* - it serves
> to define the
On Thu, Feb 28, 2019 at 5:22 PM Daniel M. Capella via aur-general
wrote:
>
> On February 28, 2019 8:58:06 AM EST, Jerome Leclanche
> wrote:
>
>
>
> >OT: We should maybe have the AUR lint PKGBUILDs on git push (and
> >reject really bad ones) if we want to improve that situation.
> >
> >J.
On February 28, 2019 12:43:02 PM EST, Eli Schwartz via aur-general
wrote:
>On 2/28/19 11:22 AM, Daniel M. Capella via aur-general wrote:
>> On February 28, 2019 8:58:06 AM EST, Jerome Leclanche
>> wrote:
>>
>>
>>
>>> OT: We should maybe have the AUR lint PKGBUILDs on git push (and
>>>
22 matches
Mail list logo
