You are not logged in.
- Topics: Active | Unanswered
#1 2007-11-21 11:27:36
- ReaphSharc
- Member
- From: the Netherlands
- Registered: 2007-11-05
- Posts: 138
- Website
PKGBUILD conventions when manually compiling a package
I' working on a PKGBUILD file for AUR. The software uses an install-script that builds and installs the package in the root (/) and it can't be configured to install in a fakeroot. It also consists of three seperate components that form the software, which all need to be compiled seperately; libraries, configuration files and the software itself.
Should I put all the code needed to compile and install the package in the fakeroot in the PKGBUILD file, or should I create a seperate install file ($pkgname.install)?
Do you want a Bubble Icon? Feel free to submit your requests or personal creations to be included in future releases.
I'm 100% Linux!
Offline
#2 2007-11-21 13:05:20
- Cerebral
- Forum Fellow
- From: Waterloo, ON, CA
- Registered: 2005-04-08
- Posts: 3,108
- Website
Re: PKGBUILD conventions when manually compiling a package
You should patch or otherwise modify the build system so that it installs to $startdir/pkg/ instead of root.
Offline
#3 2007-11-21 15:07:13
- tomk
- Forum Fellow
- From: Ireland
- Registered: 2004-07-21
- Posts: 9,839
Re: PKGBUILD conventions when manually compiling a package
Also, *.install files are used for commands that have to be run in the live system before or after the package is installed. They have no function in relation to the building of the package.
Offline
#4 2007-11-21 18:19:15
- ReaphSharc
- Member
- From: the Netherlands
- Registered: 2007-11-05
- Posts: 138
- Website
Re: PKGBUILD conventions when manually compiling a package
I'll give it a try... thanks for the advice!
Do you want a Bubble Icon? Feel free to submit your requests or personal creations to be included in future releases.
I'm 100% Linux!
Offline