You are not logged in.
- Topics: Active | Unanswered
#1 2008-10-12 13:00:14
- creslin
- Member
- Registered: 2008-10-04
- Posts: 241
Convoluted Makefiles: Best method for packaging? (e.g. Beaver)
I just picked up and updated the orphaned Beaver package. Its original Makefile installs all files to $(DESTDIR)/share/beaver and then symlinks the binary to $(DESTDIR)/bin/beaver.
My ugly "fix" for this was to patch the actual Makefile to use the standard Arch heirarchy, but I'm just wondering if there is a better solution.
This is the patch: http://aur.archlinux.org/packages/beave … file.patch
Last edited by creslin (2008-10-12 13:02:08)
ARCH|awesome3.0 powered by Pentium M 750 | 512MB DDR2-533 | Radeon X300 M
The journey is the reward.
Offline
#2 2008-10-12 13:15:26
- catwell
- Member
- From: Bretagne, France
- Registered: 2008-02-20
- Posts: 207
- Website
Re: Convoluted Makefiles: Best method for packaging? (e.g. Beaver)
If the makefile is not too long, I'd just not use it and do everything by hand with install in the PKGBUILD. If it's too long, I'd provide a custom makefile as a separate file.
Offline
#3 2008-10-12 13:27:16
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,399
- Website
Re: Convoluted Makefiles: Best method for packaging? (e.g. Beaver)
I think both your options are now pointed out. Either patch the makefile you your liking or do the installation manually. There is no real guideline so just whatever is easiest for you.
Offline
#4 2008-10-12 14:38:56
- creslin
- Member
- Registered: 2008-10-04
- Posts: 241
Re: Convoluted Makefiles: Best method for packaging? (e.g. Beaver)
Alright.. then I'll stick with the patch for this one since I already made it. Just wanted to make sure it was fine to do this way.
Last edited by creslin (2008-10-12 14:47:54)
ARCH|awesome3.0 powered by Pentium M 750 | 512MB DDR2-533 | Radeon X300 M
The journey is the reward.
Offline