[SOLVED, ignore] Lime PKGBUILD

rainbowdashc · 2013-11-14 02:57:14

I've been trying to work on a PKGBUILD for Lime, a fork of the Sublime Text editor, but I've been encountering many... difficulties.

Please help (or rewrite the PKGBUILD entirely!)

PKGBUILD

Last edited by rainbowdashc (2013-11-30 23:29:44)

Trilby · 2013-11-14 03:08:00

Why are you (trying to) copy all the source to the user's home directory before building? Regardless of why, you can't do that.

karol · 2013-11-14 03:08:37

Have a look at https://wiki.archlinux.org/index.php/Go … Guidelines

Jristz · 2013-11-14 03:21:19

pacman can't access any outside $startdir

rainbowdashc · 2013-11-14 03:26:05

To be honest, I have no idea what I'm doing, and would appreciate it if someone could write/help write a PKGBUILD. Also, the $HOME/go was a workaround for a build failure.

Last edited by rainbowdashc (2013-11-14 03:26:41)

Jristz · 2013-11-14 03:28:55

First of all, NOT access any related to $HOME, I say NO and NO, NO and NO.
so $HOME/go is wrong, the best option is $srcdir/go

rainbowdashc · 2013-11-14 03:32:05

Tweaked, I'll try re-building and seeing happens.

Edit: ...oh. This experience makes me feel stupider and stupider.

New PKGBUILD

Last edited by rainbowdashc (2013-11-14 03:46:15)

Scimmia · 2013-11-14 03:34:03

What build failure? It should be pretty simple, make a build dir, run cmake .., and make.

Forget all of this "code/go/src/lime/" crap. You misread the readme.

Last edited by Scimmia (2013-11-14 03:37:01)

rainbowdashc · 2013-11-14 03:56:05

Build errors at end.

I removed a bunch of unimportant stuff at the beginning, it exceeded the maximum paste size.

Last edited by rainbowdashc (2013-11-14 03:56:16)

Scimmia · 2013-11-14 04:06:32

OK, so change GOPATH.

rainbowdashc · 2013-11-14 04:12:25

I'm trying to figure out how exactly these folders are structured right now. Meh, I'll get some sleep for now and fix this tomorrow.

rainbowdashc · 2013-11-14 13:13:25

Tweaked the PKGBUILD (second src/ dir is a workaround):

http://pastie.org/8479969

Build errors:

http://pastie.org/8479968

Lone_Wolf · 2013-11-14 13:54:08

using a separate builddir is not uncommon, but you should copy the sourcefiles then to that dir and give it a clear name.

this is crude way to do it i've used in a few packages as an example

rm -rf ${pkgname}-build
cp -r "${_pkgname}-${pkgver}" "${srcdir}/${pkgname}-build"
cd "${srcdir}/${pkgname}-build"

(note : i'm far from a bash wizard, and there might be better ways to do it but this one works for me).

about the build errors :

backend/textmate/language.go:22: undefined: rubex.Regexp
backend/textmate/language.go:71: invalid recursive type Pattern
backend/textmate/language.go:193: undefined: rubex.Compile

It looks like you're missing a dependency, try finding out what program / language uses rubex.Regexp and rubex.Compile .
my first guess would be they are ruby extensions.

edit : typos

Last edited by Lone_Wolf (2013-11-14 13:55:21)

Scimmia · 2013-11-14 16:16:51

Lone_Wolf wrote:

using a separate builddir is not uncommon, but you should copy the sourcefiles then to that dir and give it a clear name.
this is crude way to do it i've used in a few packages as an example
rm -rf ${pkgname}-build
cp -r "${_pkgname}-${pkgver}" "${srcdir}/${pkgname}-build"
cd "${srcdir}/${pkgname}-build"

Why would you ever do that? Seriously, if that works, just build in "${_pkgname}-${pkgver}". The use of a separate build dir was used in the old pacman for VCS packages when you wanted to keep a clean copy of the source, but I can't think of another reason to do it.

I don't see anything wrong with using mv instead of copy when it absolutely must be in a dir called "src".

Lone_Wolf · 2013-11-15 18:19:47

scimmia,

for some of my packages i had to take care of building errors often.
During build the sourcefiles are sometimes changed by the build process, extra files are created and it was hard to figure out whether the cause of the build fail was in the original source or in the build process.
To be sure of that, i had to compare with a separate clean copy of the source.

Also i had occasions where i forgot to remove the src folder after a failed build, and although i had applied a fix, the non-clean state of the source caused another build fail.

Those issues were almost completely gone after i started building in a copy of the source.

Arch Linux

#1 2013-11-14 02:57:14

[SOLVED, ignore] Lime PKGBUILD

#2 2013-11-14 03:08:00

Re: [SOLVED, ignore] Lime PKGBUILD

#3 2013-11-14 03:08:37

Re: [SOLVED, ignore] Lime PKGBUILD

#4 2013-11-14 03:21:19

Re: [SOLVED, ignore] Lime PKGBUILD

#5 2013-11-14 03:26:05

Re: [SOLVED, ignore] Lime PKGBUILD

#6 2013-11-14 03:28:55

Re: [SOLVED, ignore] Lime PKGBUILD

#7 2013-11-14 03:32:05

Re: [SOLVED, ignore] Lime PKGBUILD

#8 2013-11-14 03:34:03

Re: [SOLVED, ignore] Lime PKGBUILD

#9 2013-11-14 03:56:05

Re: [SOLVED, ignore] Lime PKGBUILD

#10 2013-11-14 04:06:32

Re: [SOLVED, ignore] Lime PKGBUILD

#11 2013-11-14 04:12:25

Re: [SOLVED, ignore] Lime PKGBUILD

#12 2013-11-14 13:13:25

Re: [SOLVED, ignore] Lime PKGBUILD

#13 2013-11-14 13:54:08

Re: [SOLVED, ignore] Lime PKGBUILD

#14 2013-11-14 16:16:51

Re: [SOLVED, ignore] Lime PKGBUILD

#15 2013-11-15 18:19:47

Re: [SOLVED, ignore] Lime PKGBUILD

Board footer