[aur-dev] What should AURv4 helpers do to get packages?
Hello, In AURv4, URLPath was removed due to the introduction of Git integration, which raises the question: what is the recommended way for AUR helpers to get packages? Should they: (a) manually generate a clone URL (/PKGBASE.git/) and clone it? (b) manually generate a tarball URL (/cgit/aur.git/snapshot/PKGBASE.tar.gz) and download it? (c) do something else entirely? In other words: could you please add a RPC field with a “recommended” URL to work with? -- Chris Warrick <https://chriswarrick.com/> PGP: 5EAAEA16
On Tue, 09 Jun 2015 at 16:52:52, Chris Warrick wrote:
Hello, In AURv4, URLPath was removed due to the introduction of Git integration, which raises the question: what is the recommended way for AUR helpers to get packages? Should they:
(a) manually generate a clone URL (/PKGBASE.git/) and clone it?
Yes, please clone using Git and use `git pull` (or `git fetch`) for updates. Alternatively, if you don't care about the package base history, create a shallow clone with "--depth 1".
(b) manually generate a tarball URL (/cgit/aur.git/snapshot/PKGBASE.tar.gz) and download it?
Please don't do that. The snapshot tarballs are only designed for users who don't have access to a working Git setup.
(c) do something else entirely?
In other words: could you please add a RPC field with a “recommended” URL to work with?
I could do that. Note that I don't see a good reason for ever changing the clone URIs though (unless we switch to a completely different system again), so I am not sure whether such a field is needed.
-- Chris Warrick <https://chriswarrick.com/> PGP: 5EAAEA16
On 9 Jun 2015 22:58, "Lukas Fleischer" <lfleischer@archlinux.org> wrote:
On Tue, 09 Jun 2015 at 16:52:52, Chris Warrick wrote:
Hello, In AURv4, URLPath was removed due to the introduction of Git integration, which raises the question: what is the recommended way for AUR helpers to get packages? Should they:
(a) manually generate a clone URL (/PKGBASE.git/) and clone it?
Yes, please clone using Git and use `git pull` (or `git fetch`) for updates. Alternatively, if you don't care about the package base history, create a shallow clone with "--depth 1".
(b) manually generate a tarball URL (/cgit/aur.git/snapshot/PKGBASE.tar.gz) and download it?
Please don't do that. The snapshot tarballs are only designed for users who don't have access to a working Git setup.
(c) do something else entirely?
In other words: could you please add a RPC field with a “recommended” URL to work with?
I could do that. Note that I don't see a good reason for ever changing the clone URIs though (unless we switch to a completely different system again), so I am not sure whether such a field is needed.
Some AUR helpers (cower, aurget, ..) currently rely in this URLPath field for retrieving the correct tarball. It would be very useful to allow backward compatibility with the RPC interface v3, at least for the time being.
On Wed, 10 Jun 2015 at 04:30:15, Rémy Marquis wrote:
[...] Some AUR helpers (cower, aurget, ..) currently rely in this URLPath field for retrieving the correct tarball.
It would be very useful to allow backward compatibility with the RPC interface v3, at least for the time being.
How? The new snapshot tarballs are not source tarballs (they contain a different directory structure), so there is no point in pretending that the tarball feature still works.
On Wed, 10 Jun 2015 at 07:52:09, Lukas Fleischer wrote:
On Wed, 10 Jun 2015 at 04:30:15, Rémy Marquis wrote:
[...] Some AUR helpers (cower, aurget, ..) currently rely in this URLPath field for retrieving the correct tarball.
It would be very useful to allow backward compatibility with the RPC interface v3, at least for the time being.
How? The new snapshot tarballs are not source tarballs (they contain a different directory structure), so there is no point in pretending that the tarball feature still works.
Looks like I was mistaken about the directory structure. cgit does indeed create subdirectories with the branch name. I will add the field back for compatibility, however using it is not recommended.
On 10 Jun 2015 20:05, "Lukas Fleischer" <lfleischer@archlinux.org> wrote:
On Wed, 10 Jun 2015 at 07:52:09, Lukas Fleischer wrote:
On Wed, 10 Jun 2015 at 04:30:15, Rémy Marquis wrote:
[...] Some AUR helpers (cower, aurget, ..) currently rely in this URLPath
field
for retrieving the correct tarball.
It would be very useful to allow backward compatibility with the RPC interface v3, at least for the time being.
How? The new snapshot tarballs are not source tarballs (they contain a different directory structure), so there is no point in pretending that the tarball feature still works.
Looks like I was mistaken about the directory structure. cgit does indeed create subdirectories with the branch name. I will add the field back for compatibility, however using it is not recommended.
Thank you!
On Thu, 11 Jun 2015 at 07:12:03, Rémy Marquis wrote:
On 10 Jun 2015 20:05, "Lukas Fleischer" <lfleischer@archlinux.org> wrote:
On Wed, 10 Jun 2015 at 07:52:09, Lukas Fleischer wrote:
On Wed, 10 Jun 2015 at 04:30:15, Rémy Marquis wrote:
[...] Some AUR helpers (cower, aurget, ..) currently rely in this URLPath
field
for retrieving the correct tarball.
It would be very useful to allow backward compatibility with the RPC interface v3, at least for the time being.
How? The new snapshot tarballs are not source tarballs (they contain a different directory structure), so there is no point in pretending that the tarball feature still works.
Looks like I was mistaken about the directory structure. cgit does indeed create subdirectories with the branch name. I will add the field back for compatibility, however using it is not recommended.
Thank you!
Done, the URLPath field should be back now.
participants (3)
-
Chris Warrick
-
Lukas Fleischer
-
Rémy Marquis