Hello,
I went to through this AUR wiki page but did not get the answer.
https://wiki.archlinux.org/index.php/AUR
Is there a way to get notified when "Maintainer" updates new PKGBUILD?
We already have way to notify for new comments on AUR package. So
possibly it would be easy to extend that wi
On 2014-05-07 09:11, Amish wrote:
Hello,
I went to through this AUR wiki page but did not get the answer.
https://wiki.archlinux.org/index.php/AUR
Is there a way to get notified when "Maintainer" updates new PKGBUILD?
We already have way to notify for new comments on AUR package. So
possibly
On Wed, May 7, 2014 at 5:56 PM, Doug Newgard wrote:
> I believe cryptocrack has said that the entire notification system needs an
> overhaul, and things like this won't get implemented until that happens.
Indeed: https://bugs.archlinux.org/task/31851
On 05/08/2014 02:21 AM, Marcel Korpel wrote:
On Wed, May 7, 2014 at 5:56 PM, Doug Newgard wrote:
I believe cryptocrack has said that the entire notification system needs an
overhaul, and things like this won't get implemented until that happens.
Indeed: https://bugs.archlinux.org/task/318
On 2014-05-08 10:50 +0530
Amish wrote:
>
>
>On 05/08/2014 02:21 AM, Marcel Korpel wrote:
>> On Wed, May 7, 2014 at 5:56 PM, Doug Newgard wrote:
>>> I believe cryptocrack has said that the entire notification system needs an
>>> overhaul, and things like this won't get implemented until that happe
On 2014-05-08 14:10 +
Xyne wrote:
>To give another example, I have attached a very simple script
>that accepts a list of package names and prints out their last modification
>times in a sorted list. It depends on python3-aur.
The attachments seems to have been stripped. You can find the scrip
On 05/08/2014 07:40 PM, Xyne wrote:
On 2014-05-08 10:50 +0530
Amish wrote:
I added one line in package update Guidelines for Maintainer.
Here is the link:
https://wiki.archlinux.org/index.php/Arch_User_Repository#Maintaining_packages
Here is the line added:
"After submitting the update, l
On Thu, May 08, 2014 at 08:06:15PM +0530, Amish wrote:
On 05/08/2014 07:40 PM, Xyne wrote:
On 2014-05-08 10:50 +0530
Amish wrote:
I added one line in package update Guidelines for Maintainer.
Here is the link:
https://wiki.archlinux.org/index.php/Arch_User_Repository#Maintaining_packages
* Amish [2014-05-08 20:06:15 +0530]:
>
>
> On 05/08/2014 07:40 PM, Xyne wrote:
> >On 2014-05-08 10:50 +0530
> >Amish wrote:
> >>
> >>I added one line in package update Guidelines for Maintainer.
> >>
> >>Here is the link:
> >>https://wiki.archlinux.org/index.php/Arch_User_Repository#Maintaining_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If we ever have a proper notifocation system inbuilt, I hope it will
be optional per user because I don't want to be flooded with emails
about package updates. Seeing them in my AUR helper before updating is
also enough for me
- -- nekinie
On 08/05/1
On 05/08/2014 08:22 PM, James Bulmer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If we ever have a proper notifocation system inbuilt, I hope it will
be optional per user because I don't want to be flooded with emails
about package updates. Seeing them in my AUR helper before updating
3) I think commenting about update will involve more people and bring
awareness that the AUR package is active and not orphaned.
This is true, but should not be implemented like that. That's good it
has been reverted.
AUR could keep track of the updates, e.g. have a new field named
"Updates"
On 8 May 2014 17:09, Nowaker wrote:
>> 3) I think commenting about update will involve more people and bring
>> awareness that the AUR package is active and not orphaned.
>
>
> This is true, but should not be implemented like that. That's good it has
> been reverted.
>
> AUR could keep track of th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I agree with the subscription suggestion, users can then be imformed
of package updates that are relevent to them
- -- nekinie
On 08/05/14 17:20, WorMzy Tykashi wrote:
> On 8 May 2014 17:09, Nowaker wrote:
>>> 3) I think commenting about update will
On 2014-05-08 18:09 +0200
Nowaker wrote:
>> 3) I think commenting about update will involve more people and bring
>> awareness that the AUR package is active and not orphaned.
>
>This is true, but should not be implemented like that. That's good it
>has been reverted.
>
>AUR could keep track of t
15 matches
Mail list logo