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
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 altogether and just cares
On Mon, 31 Jul 2017 14:16:33 -0400
Eli Schwartz wrote:
> On 07/31/2017 02:09 PM, Christian Rebischke wrote:
> >> Do I really need to do this? Won't the 'git submodule update' command
> >> choose the
> >> correct commit?
> >
> > May somebody else correct me, but I don't think so. `git submodul
On 07/31/2017 02:09 PM, Christian Rebischke wrote:
>> Do I really need to do this? Won't the 'git submodule update' command choose
>> the
>> correct commit?
>
> May somebody else correct me, but I don't think so. `git submodule
> update` will just update to the HEAD of the sub repository. And we
On Mon, Jul 31, 2017 at 08:09:56PM +0200, Christian Rebischke wrote:
> On Fri, Jul 28, 2017 at 02:32:07PM +, Dan Printzell wrote:
> > Do I really need to do this? Won't the 'git submodule update' command
> > choose the
> > correct commit?
>
> May somebody else correct me, but I don't think so
On Fri, Jul 28, 2017 at 02:32:07PM +, Dan Printzell wrote:
> I could maintain other packages as well, but I would prioritize my D packages.
Thats what I wanted to hear :)
> Do I really need to do this? Won't the 'git submodule update' command choose
> the
> correct commit?
May somebody else
