[aur-general] pkgbuild - suggestion
hello, this might not be a perfect place to propose new things to pkgbuild but otoh it does affect pkgbuild and does make sense for aur packages. my point is: at the moment the only way that the aur maintainers learn about upstream version bump is either by a user notification system (flags on aur) or some external (rss for instance) checks. this may work to some extent but wouldn't it be nice if the checking function would be the part of the pkgbuild (a new function alongside prepare(), build(), package()..) and this function would be invoked by an aur wrapper such as yaourt? the implementation probably would not be trivial due to security concerns but in the end, maybe having a possibility to process an html page with a regex or read rss would be a good start. j
Hi, Le 17/02/2016 23:11, Jozef Riha a écrit :
hello,
this might not be a perfect place to propose new things to pkgbuild but otoh it does affect pkgbuild and does make sense for aur packages. my point is: at the moment the only way that the aur maintainers learn about upstream version bump is either by a user notification system (flags on aur) or some external (rss for instance) checks. this may work to some extent but wouldn't it be nice if the checking function would be the part of the pkgbuild (a new function alongside prepare(), build(), package()..) and this function would be invoked by an aur wrapper such as yaourt?
the implementation probably would not be trivial due to security concerns but in the end, maybe having a possibility to process an html page with a regex or read rss would be a good start.
They are already packages doing this sort of things (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=firefox-nightly-fr), but I don’t think it’s a good idea in general. As you said, they are already notification for packages updates from upstream, auto-updating PKGBUILD has a lot of issues (among them, security indeed, but also it goes against KISS for me).
Le 17 février 2016 23:11:03 GMT+01:00, Jozef Riha <jose1711@gmail.com> a écrit :
hello,
this might not be a perfect place to propose new things to pkgbuild but otoh it does affect pkgbuild and does make sense for aur packages. my point is: at the moment the only way that the aur maintainers learn about upstream version bump is either by a user notification system (flags on aur) or some external (rss for instance) checks. this may work to some extent but wouldn't it be nice if the checking function would be the part of the pkgbuild (a new function alongside prepare(), build(), package()..) and this function would be invoked by an aur wrapper such as yaourt?
the implementation probably would not be trivial due to security concerns but in the end, maybe having a possibility to process an html page with a regex or read rss would be a good start.
j
What do u mean exactly ? That when users install the package, some yaourt/makepkg tool sends a "feedback" of the version ? That would work mostly for CVS packages, when executing pkgver(). Wouldn't it better to have this kind of check executed on the AUR server ? But that would mean a (weekly ?) download of the package on the AUR server... Not the best solution i think :/ -- Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.
automatic notification sending is i believe a way to hell (10th+ notification for the same package would only make maintainer more angry). the idea is to only show it (when asked to) to user. then it's up to him/her to either notify maintainer, make a patch and do the update him/herself or even uninstall the package (if some serious problem has been found with the current version). On Wed, 17 Feb 2016, Félix Piédallu wrote:
Le 17 février 2016 23:11:03 GMT+01:00, Jozef Riha <jose1711@gmail.com> a écrit :
hello,
this might not be a perfect place to propose new things to pkgbuild but otoh it does affect pkgbuild and does make sense for aur packages. my point is: at the moment the only way that the aur maintainers learn about upstream version bump is either by a user notification system (flags on aur) or some external (rss for instance) checks. this may work to some extent but wouldn't it be nice if the checking function would be the part of the pkgbuild (a new function alongside prepare(), build(), package()..) and this function would be invoked by an aur wrapper such as yaourt?
the implementation probably would not be trivial due to security concerns but in the end, maybe having a possibility to process an html page with a regex or read rss would be a good start.
j
What do u mean exactly ? That when users install the package, some yaourt/makepkg tool sends a "feedback" of the version ? That would work mostly for CVS packages, when executing pkgver(). Wouldn't it better to have this kind of check executed on the AUR server ? But that would mean a (weekly ?) download of the package on the AUR server... Not the best solution i think :/
-- Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.
Sometimes there may be a new version out, but the maintainer needs to test and make sure it's working as expected. It may need a patch to work correctly, or it may have a major flaw and every other distro is also avoiding updating to the latest version. The flagging system, I feel at least, is more so there for users to nudge a maintainer if they haven't updated it. Often people can wait a few days after the upstream release for the new version, and if they can't, they should be using the -git version anyway.
i fully agree and that is exactly the reason why automatic pkgbuild update was never suggested. On Fri, Feb 19, 2016 at 12:58 AM, Justin Dray <justin@dray.be> wrote:
Sometimes there may be a new version out, but the maintainer needs to test and make sure it's working as expected. It may need a patch to work correctly, or it may have a major flaw and every other distro is also avoiding updating to the latest version. The flagging system, I feel at least, is more so there for users to nudge a maintainer if they haven't updated it. Often people can wait a few days after the upstream release for the new version, and if they can't, they should be using the -git version anyway.
On 02/17/2016 05:11 PM, Jozef Riha wrote:
hello,
this might not be a perfect place to propose new things to pkgbuild but otoh it does affect pkgbuild and does make sense for aur packages. my point is: at the moment the only way that the aur maintainers learn about upstream version bump is either by a user notification system (flags on aur) or some external (rss for instance) checks. this may work to some extent but wouldn't it be nice if the checking function would be the part of the pkgbuild (a new function alongside prepare(), build(), package()..) and this function would be invoked by an aur wrapper such as yaourt?
the implementation probably would not be trivial due to security concerns but in the end, maybe having a possibility to process an html page with a regex or read rss would be a good start.
j
As you rightly pointed out, that is the job of the AUR *maintainer*. Check out urlwatch... -- Eli Schwartz
* Eli Schwartz <eschwartz93@gmail.com> [2016-02-17 19:50:40 -0500]:
On 02/17/2016 05:11 PM, Jozef Riha wrote:
hello,
this might not be a perfect place to propose new things to pkgbuild but otoh it does affect pkgbuild and does make sense for aur packages. my point is: at the moment the only way that the aur maintainers learn about upstream version bump is either by a user notification system (flags on aur) or some external (rss for instance) checks. this may work to some extent but wouldn't it be nice if the checking function would be the part of the pkgbuild (a new function alongside prepare(), build(), package()..) and this function would be invoked by an aur wrapper such as yaourt?
the implementation probably would not be trivial due to security concerns but in the end, maybe having a possibility to process an html page with a regex or read rss would be a good start.
j
As you rightly pointed out, that is the job of the AUR *maintainer*.
Check out urlwatch...
Oh, interesting. I wrote http://git.the-compiler.org/webdiff/tree/webdiff some while ago because I couldn't find anything like that, but urlwatch sounds like a bit more powerful. Definitely need to check it out! Florian -- http://www.the-compiler.org | me@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/
Arch Linux CN community have a tool nvchecker ( https://github.com/lilydjwg/nvchecker) for periodically checking new versions of software and sending notifications. We have a nightly building bot and a unofficial repo ( https://github.com/archlinuxcn/repo) driving by nvchecker. On Thu, Feb 18, 2016 at 2:39 PM, Florian Bruhin <me@the-compiler.org> wrote:
On 02/17/2016 05:11 PM, Jozef Riha wrote:
hello,
this might not be a perfect place to propose new things to pkgbuild but otoh it does affect pkgbuild and does make sense for aur packages. my
is: at the moment the only way that the aur maintainers learn about upstream version bump is either by a user notification system (flags on aur) or some external (rss for instance) checks. this may work to some extent but wouldn't it be nice if the checking function would be the
of the pkgbuild (a new function alongside prepare(), build(),
* Eli Schwartz <eschwartz93@gmail.com> [2016-02-17 19:50:40 -0500]: point part package()..)
and this function would be invoked by an aur wrapper such as yaourt?
the implementation probably would not be trivial due to security concerns but in the end, maybe having a possibility to process an html page with a regex or read rss would be a good start.
j
As you rightly pointed out, that is the job of the AUR *maintainer*.
Check out urlwatch...
Oh, interesting. I wrote http://git.the-compiler.org/webdiff/tree/webdiff some while ago because I couldn't find anything like that, but urlwatch sounds like a bit more powerful. Definitely need to check it out!
Florian
-- http://www.the-compiler.org | me@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/
-- -------------------------------------------------------------------------------- Jiachen Yang 楊嘉晨 Graduate School of Information Science and Technology, Osaka University Tel: 080-3853-2770 MSN: firechildren@hotmail.com GMail: farseerfc@gmail.com
i think it is the job of a maintainer to keep the pkgbuild updated (while buildable at the same time). with keeping an eye on new upstream releases.. not sure. why the "notify" button on aur webpage exists in the first place. and then you also have pkgbuilds that lost their maintainers, maintainer became unresponsive (is on vacation, ill, whatever). in such cases you probably still want to be updated or at least be informed there are updates pending. to be honest i did not think this through - having defined this as a function would indeed require repetitious pull from aur server which isn't ideal. running weekly checks on aur server itself i believe really defeats the kiss principle and picturing myself as an aur maintainer i would not like to do it. thank you for suggesting urlwatch - seems like a nice tool that simply does the job. i was able to quickly cobble a oneliner to keep track of my favourite tool: gpsprune. all i had to do was just put the gpsprune website to urls.txt and define a hook that parses the useful information (i certainly do not want to watch changes on the whole page). in the end it looks like this: def filter(url, data): m = re.search(r'.*Runnable code(.+)\.jar.*',html2txt.html2text(data, method='re'), re.MULTILINE) return m.group(1) now what if this is defined inside pkgbuild on a single line (so that it stays in the local db), for instance like this: UrlWatcher=('http://activityworkshop.net/software/gpsprune/download.html','.*Runnable code(.+)\.jar.*',1) i don't think this leaves much space for attacks on system security/integrity - the arguments are being parsed by urlwatcher, not executed. so the idea is that i normally do yaourt -Syu --aur daily at present. wouldn't it be nice if one could do (say - once a week) yaourt -Syu --aur --check-up-stream-changes and get: * gpsprune - possibly a new upstream version detected ? cheers, jose On Wed, 17 Feb 2016, Eli Schwartz wrote:
On 02/17/2016 05:11 PM, Jozef Riha wrote:
hello,
this might not be a perfect place to propose new things to pkgbuild but otoh it does affect pkgbuild and does make sense for aur packages. my point is: at the moment the only way that the aur maintainers learn about upstream version bump is either by a user notification system (flags on aur) or some external (rss for instance) checks. this may work to some extent but wouldn't it be nice if the checking function would be the part of the pkgbuild (a new function alongside prepare(), build(), package()..) and this function would be invoked by an aur wrapper such as yaourt?
the implementation probably would not be trivial due to security concerns but in the end, maybe having a possibility to process an html page with a regex or read rss would be a good start.
j
As you rightly pointed out, that is the job of the AUR *maintainer*.
Check out urlwatch...
-- Eli Schwartz
participants (8)
-
Bruno Pagani
-
Eli Schwartz
-
Florian Bruhin
-
Félix Piédallu
-
Jiachen Yang
-
Jose Riha
-
Jozef Riha
-
Justin Dray