From: Vesa Kaihlavirta
Signed-off-by: Vesa Kaihlavirta
---
scripts/makepkg.sh.in | 15 ---
1 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in
index 5bbd880..78b1e22 100644
--- a/scripts/makepkg.sh.in
+++ b/scripts/makepkg.
Vesa Kaihlavirta wrote:
From: Vesa Kaihlavirta
Signed-off-by: Vesa Kaihlavirta
---
scripts/makepkg.sh.in | 15 ---
1 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in
index 5bbd880..78b1e22 100644
--- a/scripts/makepkg.sh
> Why is this useful? I see that you can either you use the --holdver flag
> or you check out a specific revision in the PKGBUILD.
For software that make their release versions only in svc. E.g. my go
package in community. I want to have holdver every time I build this
package, and it's much mor
Vesa Kaihlavirta wrote:
Why is this useful? I see that you can either you use the --holdver flag
or you check out a specific revision in the PKGBUILD.
For software that make their release versions only in svc. E.g. my go
package in community. I want to have holdver every time I build this
pac
On Wed, Jan 20, 2010 at 11:55 AM, Allan McRae wrote:
>
>
> As an aside, looking at holdver makes me realize just how stupid it is. It
> does not hold the checkout at the version specified, which I bet most people
> thinks it will. It just stop the pkgver being updated. e.g. I just build
> makepk
On Wed, Jan 20, 2010 at 1:43 PM, Xavier Chantry wrote:
> On Wed, Jan 20, 2010 at 11:55 AM, Allan McRae wrote:
>>
>>
>> As an aside, looking at holdver makes me realize just how stupid it is. It
>> does not hold the checkout at the version specified, which I bet most people
>> thinks it will. It
