[arch-general] Frequency of abs updates, would increasing frequency cost much?
This is more a general question, I understand abs is updated every 24 hours. Would more regular updates (say, every 1 hour or so) be better? Currently, for those (like me) who compulsively update, abs is pretty much guaranteed to be behind the latest packages in any mirror (by a max of 24 hours). If it doesn't cost (resources etc.) too much for abs to be updated every 1 hour, wouldn't this mean that most mirrors are likely to be in sync with abs just about all the time? Obviously I've got self-interest in this, since I auto-patch (using bauerbill) some packages from the repos. Its not a huge priority (I can manually access the SVN interface, but I think it'd be useful.
On 31/01/11 16:27, Ng Oon-Ee wrote:
This is more a general question, I understand abs is updated every 24 hours. Would more regular updates (say, every 1 hour or so) be better?
Currently, for those (like me) who compulsively update, abs is pretty much guaranteed to be behind the latest packages in any mirror (by a max of 24 hours). If it doesn't cost (resources etc.) too much for abs to be updated every 1 hour, wouldn't this mean that most mirrors are likely to be in sync with abs just about all the time?
Obviously I've got self-interest in this, since I auto-patch (using bauerbill) some packages from the repos. Its not a huge priority (I can manually access the SVN interface, but I think it'd be useful.
The ABS update is quite inefficient... it takes about 15 minutes to run. If this was improved, then I would see no reason not to run it every hour. Saying that, I seem to remember that we were going to run this a few more times a day, but I have no idea what happened to that... Allan
On Mon, 2011-01-31 at 17:21 +1000, Allan McRae wrote:
On 31/01/11 16:27, Ng Oon-Ee wrote:
This is more a general question, I understand abs is updated every 24 hours. Would more regular updates (say, every 1 hour or so) be better?
Currently, for those (like me) who compulsively update, abs is pretty much guaranteed to be behind the latest packages in any mirror (by a max of 24 hours). If it doesn't cost (resources etc.) too much for abs to be updated every 1 hour, wouldn't this mean that most mirrors are likely to be in sync with abs just about all the time?
Obviously I've got self-interest in this, since I auto-patch (using bauerbill) some packages from the repos. Its not a huge priority (I can manually access the SVN interface, but I think it'd be useful.
The ABS update is quite inefficient... it takes about 15 minutes to run. If this was improved, then I would see no reason not to run it every hour. Saying that, I seem to remember that we were going to run this a few more times a day, but I have no idea what happened to that...
Allan
Ah, I had no idea it took so long. In that case it wouldn't make sense to have it run so often, of course. Doesn't it simply tar everything in the directory?
On Jan 31, 2011 1:15 AM, "Allan McRae" <allan@archlinux.org> wrote:
On 31/01/11 16:27, Ng Oon-Ee wrote:
This is more a general question, I understand abs is updated every 24 hours. Would more regular updates (say, every 1 hour or so) be better?
Currently, for those (like me) who compulsively update, abs is pretty much guaranteed to be behind the latest packages in any mirror (by a max of 24 hours). If it doesn't cost (resources etc.) too much for abs to be updated every 1 hour, wouldn't this mean that most mirrors are likely to be in sync with abs just about all the time?
Obviously I've got self-interest in this, since I auto-patch (using bauerbill) some packages from the repos. Its not a huge priority (I can manually access the SVN interface, but I think it'd be useful.
The ABS update is quite inefficient... it takes about 15 minutes to run.
If this was improved, then I would see no reason not to run it every hour. Saying that, I seem to remember that we were going to run this a few more times a day, but I have no idea what happened to that... I encountered this recently as well; what if we distributed the PKGBUILDs inside the packages? Most are very small AFAIK, and I would like this approach. Or even distribute pkg.src.xz right next to packages? C Anthony [mobile]
Am 31.01.2011 07:27, schrieb Ng Oon-Ee:
This is more a general question, I understand abs is updated every 24 hours. Would more regular updates (say, every 1 hour or so) be better?
A bit off-topic: You don't have to use ABS if you don't need a complete tree. For a single package: svn co svn://svn.archlinux.org/packages/$pkgname/trunk or svn co svn://svn.archlinux.org/packages/$pkgname/repos/testing-i686 or similar. Replace 'packages' with 'community' for community and multilib packages. This gives direct access to the subversion tree, so it is instant on updates. However, if people start trying to checkout the complete tree, we will shut it down, as subversion is incredibly inefficient. You can also pull the git tree (see [1]), which is updated every two hours, if you need the complete tree. [1] https://projects.archlinux.org/svntogit/
On Mon, 2011-01-31 at 10:18 +0100, Thomas Bächler wrote:
Am 31.01.2011 07:27, schrieb Ng Oon-Ee:
This is more a general question, I understand abs is updated every 24 hours. Would more regular updates (say, every 1 hour or so) be better?
A bit off-topic: You don't have to use ABS if you don't need a complete tree.
For a single package:
svn co svn://svn.archlinux.org/packages/$pkgname/trunk or svn co svn://svn.archlinux.org/packages/$pkgname/repos/testing-i686 or similar. Replace 'packages' with 'community' for community and multilib packages. This gives direct access to the subversion tree, so it is instant on updates. However, if people start trying to checkout the complete tree, we will shut it down, as subversion is incredibly inefficient.
You can also pull the git tree (see [1]), which is updated every two hours, if you need the complete tree.
Indeed this is the easy way out, when there was the svn webui you could download a tar. When i want to rebuild a package I always grabbed it from the website. Providing a whole abs tree updated every hour seems a bit too much overhead if you ask me. If you want the latest pkgbuild of foo just checkout the web ui or svn. I can't imagine a user waiting for a updated package of foo when there is a new version out and he wants to rebuild. (He just does that himself) To rest my case, i think the current situation is good enough. -- Jelle van der Waa
On 31 January 2011 17:45, Jelle van der Waa <jelle@vdwaa.nl> wrote:
On Mon, 2011-01-31 at 10:18 +0100, Thomas Bächler wrote:
Am 31.01.2011 07:27, schrieb Ng Oon-Ee:
This is more a general question, I understand abs is updated every 24 hours. Would more regular updates (say, every 1 hour or so) be better?
A bit off-topic: You don't have to use ABS if you don't need a complete tree.
For a single package:
svn co svn://svn.archlinux.org/packages/$pkgname/trunk or svn co svn://svn.archlinux.org/packages/$pkgname/repos/testing-i686 or similar. Replace 'packages' with 'community' for community and multilib packages. This gives direct access to the subversion tree, so it is instant on updates. However, if people start trying to checkout the complete tree, we will shut it down, as subversion is incredibly inefficient.
You can also pull the git tree (see [1]), which is updated every two hours, if you need the complete tree.
Indeed this is the easy way out, when there was the svn webui you could download a tar. When i want to rebuild a package I always grabbed it from the website.
Providing a whole abs tree updated every hour seems a bit too much overhead if you ask me. If you want the latest pkgbuild of foo just checkout the web ui or svn.
I can't imagine a user waiting for a updated package of foo when there is a new version out and he wants to rebuild. (He just does that himself)
To rest my case, i think the current situation is good enough.
He already mentioned that he can "manually access the SVN interface". He needs the ABS way because he's using bauerbill to patch up stuff. So you should bug the bauerbill author to include some kind of alternative, say, SVN/GIT support.
On Mon, 2011-01-31 at 18:45 +0800, Ray Rashif wrote:
On 31 January 2011 17:45, Jelle van der Waa <jelle@vdwaa.nl> wrote:
I can't imagine a user waiting for a updated package of foo when there is a new version out and he wants to rebuild. (He just does that himself)
To rest my case, i think the current situation is good enough.
He already mentioned that he can "manually access the SVN interface". He needs the ABS way because he's using bauerbill to patch up stuff.
So you should bug the bauerbill author to include some kind of alternative, say, SVN/GIT support.
Thanks Ray, that's precisely the situation. And I did bug the author prior to posting her, who replied that he wouldn't =). Fair enough, its kinda a niche requirement in any case.
On Mon, 2011-01-31 at 19:00 +0800, Ng Oon-Ee wrote:
On Mon, 2011-01-31 at 18:45 +0800, Ray Rashif wrote:
On 31 January 2011 17:45, Jelle van der Waa <jelle@vdwaa.nl> wrote:
I can't imagine a user waiting for a updated package of foo when there is a new version out and he wants to rebuild. (He just does that himself)
To rest my case, i think the current situation is good enough.
He already mentioned that he can "manually access the SVN interface". He needs the ABS way because he's using bauerbill to patch up stuff.
So you should bug the bauerbill author to include some kind of alternative, say, SVN/GIT support.
Thanks Ray, that's precisely the situation.
And I did bug the author prior to posting her, who replied that he wouldn't =). Fair enough, its kinda a niche requirement in any case.
Ah, i misunderstood, sorry ;) -- Jelle van der Waa
participants (6)
-
Allan McRae
-
C Anthony Risinger
-
Jelle van der Waa
-
Ng Oon-Ee
-
Ray Rashif
-
Thomas Bächler