Re: [aur-general] libgroove package review, round 2

2014-10-15 Thread Marcel Korpel
* Jeremy Audet (Wed, 15 Oct 2014 13:34:57 -0400): > A, so that's the functional difference between `prepare` and > `package`! And in prepare(), build() and check() you shouldn't touch $pkgdir! > Thanks. I haven't tested any of my packages with `--noextract`, but > I'll spend some time gettin

Re: [aur-general] libgroove package review, round 2

2014-10-15 Thread Jeremy Audet
> --noextract​ A, so that's the functional difference between `prepare` and `package`! Thanks. I haven't tested any of my packages with `--noextract`, but I'll spend some time getting familiar with that option. — Jeremy "Ichimonji10" Audet

Re: [aur-general] libgroove package review, round 2

2014-10-15 Thread Marcel Korpel
* Jeremy Audet (Tue, 14 Oct 2014 23:17:03 -0400): > Upstream has added a sample pkg-config config file to their source > code. I'd like to install a slightly modified version of that config > file to users' systems. The question is this: when do I make those > minor modifications? Should I copy an

[aur-general] libgroove package review, round 2

2014-10-14 Thread Jeremy Audet
Hi all, I'm hoping to push a change [1] [2] to my libgroove package. I know that the change _works_, but I'm not sure if it's _correct_. Upstream has added a sample pkg-config config file to their source code. I'd like to install a slightly modified version of that config file to users' systems.