Re: [aur-general] [pacman-dev] Handling git submodules (Was: Re: TU Application: Dan Printzell)

On Wed, 02 Aug 2017 20:37:49 + Dan Printzell wrote: > Excerpts from Dan B via aur-general's message of July 31, 2017 10:25 pm: > >Here's how I was told the correct way to handle it was: > >https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=mono-git#n57 > > From what I

Re: [aur-general] [pacman-dev] Handling git submodules (Was: Re: TU Application: Dan Printzell)

Excerpts from Dan B via aur-general's message of July 31, 2017 10:25 pm: Here's how I was told the correct way to handle it was: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=mono-git#n57 From what I can gather in this thread is that I don't need to #commit= any submodules. I can keep

Re: [aur-general] [pacman-dev] Handling git submodules (Was: Re: TU Application: Dan Printzell)

Here's how I was told the correct way to handle it was: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=mono-git#n57 I've got a few more that use git submodules as well: ags-git and rofi-git are ones I know offhand. > Implement noextract=() for source/git.sh to avoid having two checkouts

[aur-general] [pacman-dev] Handling git submodules (Was: Re: TU Application: Dan Printzell)

On 07/31/2017 03:35 PM, Doug Newgard wrote: > On Mon, 31 Jul 2017 14:16:33 -0400 > Eli Schwartz wrote: >> You're both right and wrong. "$srcdir/$submodulename" will be at >> origin/master, but `git submodule update` in the primary repo will >> completely ignore that clone