[arch-dev-public] Updating ABS
There have been a lot of changes going on to the repos and ABS needs updated to reflect these. As it see it the following need fixed: 1) arch=('any') support Fix commited to git 2) split package support Currently the PKGBUILD is only found in /var/abs/$repo/$pkgbase. This would make it difficult to find a split package directly. Should the db-scripts add symlinks from $pkgbase to ${pkgname[@]}? That would have a bonus effect of reserving at the split package names. 3) community support I can see this being achieved in two ways - svn2abs is run on sigurd then rsynced to gerolde - svn2abs is run directly on gerolde (requires complete svn checkout on gerolde) The second is easier but uses a bit more resources. 4) community-testing support. Comes directly as part of #3 but will need to be added to the abs.conf file So should we do anything for #2 (requires changes to db-scripts) and which is the best way to go for #3? Allan
Am Samstag 25 Juli 2009 04:27:50 schrieb Allan McRae:
2) split package support Currently the PKGBUILD is only found in /var/abs/$repo/$pkgbase. This would make it difficult to find a split package directly. Should the db-scripts add symlinks from $pkgbase to ${pkgname[@]}? That would have a bonus effect of reserving at the split package names.
Where should that symlink be? In the users /var/abs dir? And how could db- scripts do that? -- Pierre Schmitz, http://users.archlinux.de/~pierre
Pierre Schmitz wrote:
Am Samstag 25 Juli 2009 04:27:50 schrieb Allan McRae:
2) split package support Currently the PKGBUILD is only found in /var/abs/$repo/$pkgbase. This would make it difficult to find a split package directly. Should the db-scripts add symlinks from $pkgbase to ${pkgname[@]}? That would have a bonus effect of reserving at the split package names.
Where should that symlink be? In the users /var/abs dir? And how could db- scripts do that?
My idea was symlinks in SVN. When db-scripts find a package with pkgbase set, it should create symlinks for each of ${pkgname[*]} to $pkgbase (provided $pkgname[?] != $pkgbase). If the symlink exists, they should check that it is already pointing to the right folder or otherwise there could be multiple packages with the same name. Allan
Am Samstag 25 Juli 2009 11:41:13 schrieb Allan McRae:
My idea was symlinks in SVN. When db-scripts find a package with pkgbase set, it should create symlinks for each of ${pkgname[*]} to $pkgbase (provided $pkgname[?] != $pkgbase). If the symlink exists, they should check that it is already pointing to the right folder or otherwise there could be multiple packages with the same name.
What if a split pacakge was removed or moved to another pkgbase? The problem about symlinks is that they only point into one direction. In addition to this symlinks in svn aren't supported that great. I wonder if we really need it. If you want to checkout a package, move or delete it you have to use pkgbase. For abs you either checkout the complete repo or you have to use pkgbase. And because abs is about PKGBUILDs and sources but not actual packages this seems quite natural to me. They only problem I see atm. is that we might not able to detect split packages with the same pkgname. Symlinks solve this but we'll still have the problems mentioned above. I am not sure what an alternative solution to this problem might be. Perhaps a pkgname database for each repo and arch? Pierre -- Pierre Schmitz, http://users.archlinux.de/~pierre
Am Samstag 25 Juli 2009 04:27:50 schrieb Allan McRae:
3) community support I can see this being achieved in two ways - svn2abs is run on sigurd then rsynced to gerolde - svn2abs is run directly on gerolde (requires complete svn checkout on gerolde) The second is easier but uses a bit more resources.
Afaik we need to copy the repo over to gerolde anyway. E.g. for the websvn etc.. As this can be updated incrementally it should not be a big problem. -- Pierre Schmitz, http://users.archlinux.de/~pierre
participants (2)
-
Allan McRae
-
Pierre Schmitz