[Solved] Building packages from git bisect

FlowIt · 2015-06-24 11:24:12

I am bisecting a library and have to install it to /usr since the affected programs only look there. So I decided to build a package in each step of the bisect. But how must the PKGBUILD look like? I can build a tarball each time and specify it as source, but as I see it this tarball contains only the current sourcefiles, not the code from one specific commit.
I also thought of taking the easy way with ./configure --prefix=/usr && make && make install. Will this be problematic if the library is already installed by pacman?
Regards

Last edited by FlowIt (2015-06-24 17:18:05)

Trilby · 2015-06-24 11:32:38

You can use a VCS PKGBUILD and (maybe) put the bisect commands in the build function. Then just run makepkg with the `-e` flag to use the current source tree on each repetition.

(note: I've not really used git bisect myself, so this is untested.)

ugjka · 2015-06-24 11:59:29

Once you have got your git repo in src directory you can just remove the source from the PKGBUILD and do git bisect in the src directory manually via command line. Makepkg doesn't care if there is no source listed in the PKGBUILD as long as you have something in src directory, so you can just rebuild after every bisect step.

Last edited by ugjka (2015-06-24 12:02:19)

Trilby · 2015-06-24 12:01:47

ugjka, would that be equivalent to useing `makepkg -e`, or am I missing part of it?

ugjka · 2015-06-24 12:07:33

Trilby wrote:

ugjka, would that be equivalent to useing `makepkg -e`, or am I missing part of it?

I guess you're right, didn't know about -e

FlowIt · 2015-06-24 12:31:50

And will the make command issued in the PKGBUILD really build the currently checked out commit?

So just to sum things up:
This will be the directory structure:

.
|-src/
|---.git/
|---configure.ac
|---src/
|-----main.c
|-----foo.c
|-PKGBUILD

And the only change the PKGBUILD needs is to write source=()
The package will be build with makepkg -e
Manual bisecting between the builds.

WorMzy · 2015-06-24 12:33:18

I build in a clean chroot, so when I bisect, I usually have two copies of the git repository -- one in my home directory, which I carry out the bisect commands on, and one in the build directory, pulled in by the source array in the PKGBUILD. I use "#commit=<hash>" at the end of the git source declaration to build the commit that bisect tells me to check next.

Trilby · 2015-06-24 12:35:54

You can either change the source array or use the -e flag to makepkg - the latter sounds easier to me, but they'd have the same effect. There is no need to do both (though there'd also be no harm).

The make command in the PKGBUILD will build whatever is currently in the source directory, so if you've just checked out a specific commit (in the source directory) before running makepkg, then yes, that is what will build.

FlowIt · 2015-06-24 17:17:52

I chose Trilby's solution and it worked fine for me. Thanks.
I'll mark this topic as solved.

Arch Linux

#1 2015-06-24 11:24:12

[Solved] Building packages from git bisect

#2 2015-06-24 11:32:38

Re: [Solved] Building packages from git bisect

#3 2015-06-24 11:59:29

Re: [Solved] Building packages from git bisect

#4 2015-06-24 12:01:47

Re: [Solved] Building packages from git bisect

#5 2015-06-24 12:07:33

Re: [Solved] Building packages from git bisect

#6 2015-06-24 12:31:50

Re: [Solved] Building packages from git bisect

#7 2015-06-24 12:33:18

Re: [Solved] Building packages from git bisect

#8 2015-06-24 12:35:54

Re: [Solved] Building packages from git bisect

#9 2015-06-24 17:17:52

Re: [Solved] Building packages from git bisect

Board footer