Package needs access to home directory

dcc24 · 2010-04-03 11:50:23

I'm trying to package something which has a build script that requires access to the user's home directory. This is not my choice, the upstream script is coded that way.

Since makepkg works in a fakeroot environment, build fails with something like:

Specified destination directory cannot be created: /root/some/thing/

Any ideas how to resolve this?

jurkan · 2010-04-03 12:01:31

Quick and dirty: Creating /root in $pkgdir before compiling/installing. You can remove it after the make install or better copy the contents of the created folder over to /usr/share/$pkgname and create a .install-skript that informs the user to copy over the needed configuration files in his home.

Something like this:

mkdir $pkgdir/root
make || return 1
make install || return 1
mkdir -p $pkgdir/usr/share/$pkdir
mv $pkgdir/root/.whatever/ $pkgdir/usr/share/$pkgdir/
rm -R $pkgdir/root/

But I don't know whether this is the best solution.

Last edited by jurkan (2010-04-03 12:03:41)

flamelab · 2010-04-03 12:05:19

dcc24 wrote:

I'm trying to package something which has a build script that requires access to the user's home directory. This is not my choice, the upstream script is coded that way.
Since makepkg works in a fakeroot environment, build fails with something like:
Specified destination directory cannot be created: /root/some/thing/
Any ideas how to resolve this?

Could you give us the url to the script so that we can find a workaround ?

dcc24 · 2010-04-03 12:07:25

@jurkan: As a last resort, that could be used but I'd really prefer a cleaner alternative. Thanks anyway

@flamelab: Well, of course

Deps: libvorbis vorbis-tools mercurial lame maven

http://code.google.com/p/quake2-gwt-por … AndRunning

Also note that if I follow those directions myself (i.e. not with makepkg) it works perfectly fine.

Last edited by dcc24 (2010-04-03 12:08:51)

flamelab · 2010-04-03 12:12:29

I see. You can translate the scripts' code into PKGBUILD's bash code in the build() function, instead of running them directly.

For example, "build-dedicated-server" --> instead of running (for example) --> cd $srcdir/quake2-gwt-port/ && ./build-dedicated-server
do

cd $srcdir/quake2-gwt-port/maven-build
./mvn clean install

(the code and paths should be different, I just give an example).

dcc24 · 2010-04-03 14:07:33

Unfortunately that doesn't work. The error seems to be in some deeper place. If only people knew better not to hardcode paths into their scripts.

Arch Linux

#1 2010-04-03 11:50:23

Package needs access to home directory

#2 2010-04-03 12:01:31

Re: Package needs access to home directory

#3 2010-04-03 12:05:19

Re: Package needs access to home directory

#4 2010-04-03 12:07:25

Re: Package needs access to home directory

#5 2010-04-03 12:12:29

Re: Package needs access to home directory

#6 2010-04-03 14:07:33

Re: Package needs access to home directory

Board footer