[pacman-dev] Download sources from git/hg/etc
Hello, I would add a new feature in makepkg, which allow downloading of git/hg/cvs/etc content directly by makepkg. This feature can be great for packages in AUR. We have a lot of -git packages which can use this to escape to do it manually each time. I looked over the code and there is a design choice to make. Currently sources url is [filename::]http://toto. If we want to know which kind of url is (regular / git / hg) we need to have this information in PKGBUILD because git can download from http/ftp/git protocol. We can have many array in PKGBUILD as source=("http://toto") gitsouce=("git://toto.git) hgsource=("http://otot.hg) or have a more complex url syntax like [type:::][filename::]http://toto where type can be git/hg/cvs/etc. What do you think? -- Sébastien Luttringer www.seblu.net
This is already there for hg. All you need is to define _hgroot and _hgrepo variables in the PKGBUILD. eg.: http://aur.archlinux.org/packages/smem-hg/PKGBUILD Other than that, I think it'd be nice. On 4 July 2011 19:43, <seblu@seblu.net> wrote:
Hello,
I would add a new feature in makepkg, which allow downloading of git/hg/cvs/etc content directly by makepkg. This feature can be great for packages in AUR. We have a lot of -git packages which can use this to escape to do it manually each time.
I looked over the code and there is a design choice to make. Currently sources url is [filename::]http://toto. If we want to know which kind of url is (regular / git / hg) we need to have this information in PKGBUILD because git can download from http/ftp/git protocol.
We can have many array in PKGBUILD as source=("http://toto") gitsouce=("git://toto.git) hgsource=("http://otot.hg)
or have a more complex url syntax like [type:::][filename::]http://toto where type can be git/hg/cvs/etc.
What do you think?
-- Sébastien Luttringer www.seblu.net
-- Ivan c00kiemon5ter V Kanakarakis LiknedIn Profile <http://www.linkedin.com/in/c00kiemon5ter> • Personal Blog<http://c00kiemon5ter.github.com/> • Code Repository <http://github.com/c00kiemon5ter>
This is already there for hg. All you need is to define _hgroot and _hgrepo variables in the PKGBUILD.
eg.: http://aur.archlinux.org/packages/smem-hg/PKGBUILD
Other than that, I think it'd be nice. I plan to replace this, because _gitroot / _hgroot, it's only to
On Mon, Jul 4, 2011 at 7:15 PM, Ivan Kanak <ivan.kanak@gmail.com> wrote: package version as far i see. Not checkout. -- Sébastien Luttringer www.seblu.net
On Mon, Jul 04, 2011 at 06:43:47PM +0200, seblu@seblu.net wrote:
Hello,
I would add a new feature in makepkg, which allow downloading of git/hg/cvs/etc content directly by makepkg. This feature can be great for packages in AUR. We have a lot of -git packages which can use this to escape to do it manually each time.
Wouldn't this just be extending the already in place functionality that we have for source retrieval? Why would this be a separate feature?
I looked over the code and there is a design choice to make. Currently sources url is [filename::]http://toto. If we want to know which kind of url is (regular / git / hg) we need to have this information in PKGBUILD because git can download from http/ftp/git protocol.
We can have many array in PKGBUILD as source=("http://toto") gitsouce=("git://toto.git) hgsource=("http://otot.hg)
or have a more complex url syntax like [type:::][filename::]http://toto where type can be git/hg/cvs/etc.
What do you think?
I'm more in favor of reusing the variables already in place and not inventing more VCS specific vars. That said, I think data storage and retreival is one of the least pressing issues in implementing this. Whether you iterate over an array and assign, or iterate over another array, parse and assign is trivial -- we can decide on that once the rest of it is done. In other words, a lack of a decision here shouldn't stop you. Pick something and go with it. dave
On 05/07/11 02:43, seblu@seblu.net wrote:
Hello,
I would add a new feature in makepkg, which allow downloading of git/hg/cvs/etc content directly by makepkg. This feature can be great for packages in AUR. We have a lot of -git packages which can use this to escape to do it manually each time.
I looked over the code and there is a design choice to make. Currently sources url is [filename::]http://toto. If we want to know which kind of url is (regular / git / hg) we need to have this information in PKGBUILD because git can download from http/ftp/git protocol.
We can have many array in PKGBUILD as source=("http://toto") gitsouce=("git://toto.git) hgsource=("http://otot.hg)
or have a more complex url syntax like [type:::][filename::]http://toto where type can be git/hg/cvs/etc.
What do you think?
Just to catch you up on work that has already been done here: The start of a wiki page to formulate ideas on the VCS overhaul: https://wiki.archlinux.org/index.php/User:Allan/Makepkg_VCS_overhaul Two patches that do most of this work already: http://mailman.archlinux.org/pipermail/pacman-dev/2010-November/012017.html http://mailman.archlinux.org/pipermail/pacman-dev/2010-November/012018.html And looking at that thread, I promised to review those when less busy and never actually got there. I still do have them flagged on my patch queue... Also, this is something that I think would be good to target for our pacman-4.0 release if people are willing to do the work. Breaking VCS PKGBUILDs on a 4.0 release seems better idea than on a 4.1 release. Allan
Hi, I'd like to help improving this feature. So if you don't mind Seblu we can work together on it. The first step we can take is review the patches mentioned by Allan. They seem to be a good beginning for the implementation. @Allan is there already a deadline for the release of pacman 4.0? Kind regards, Andrwe
On Tue, Jul 5, 2011 at 3:58 AM, Andrwe <archlinux@andrwe.org> wrote:
Hi,
I'd like to help improving this feature. So if you don't mind Seblu we can work together on it.
The first step we can take is review the patches mentioned by Allan. They seem to be a good beginning for the implementation. Make sure you check out the bug tracker too, for instance: https://bugs.archlinux.org/task/16872?project=3
Note that there isn't one bug here, take a look at related tab and note the nine (!) linked bugs/feature requests.
@Allan is there already a deadline for the release of pacman 4.0? No, but I am shooting for sometime by the end of this month, however ambitious that may be.
-Dan
On Tue, Jul 5, 2011 at 5:17 PM, Dan McGee <dpmcgee@gmail.com> wrote:
On Tue, Jul 5, 2011 at 3:58 AM, Andrwe <archlinux@andrwe.org> wrote:
Hi,
I'd like to help improving this feature. So if you don't mind Seblu we can work together on it. It does not ask me any problem. We just need not code the same thing twice.
The first step we can take is review the patches mentioned by Allan. They seem to be a good beginning for the implementation.
Make sure you check out the bug tracker too, for instance: https://bugs.archlinux.org/task/16872?project=3
Note that there isn't one bug here, take a look at related tab and note the nine (!) linked bugs/feature requests.
@Allan is there already a deadline for the release of pacman 4.0? No, but I am shooting for sometime by the end of this month, however ambitious that may be.
I will process all the bugs and links you have pointed. -- Sébastien Luttringer www.seblu.net
participants (7)
-
Allan McRae
-
Andrwe
-
Dan McGee
-
Dave Reisner
-
Ivan Kanak
-
Seblu
-
seblu＠seblu.net