Better multiarch pkgbuilds or each port their own one?

AndyRTR · 2005-12-27 22:50:04

I´ve found this in frugalbuilds:

depends=('esd' 'lame' 'libtheora' 'libdv' 'cdparanoia' 'termcap' 'libmad'
'libungif' 'xvidcore' 'aalib' 'lzo' 'sdl' 'ffmpeg' 'libjpeg')
[ "$CARCH" == "i686" ] && depends=(${depends[@]} 'codecs')

and

[ "$CARCH" != "x86_64" ] && Fpatch $pkgname-1.0pre7-gcc4.patch
[ "$CARCH" == "x86_64" ] && Fpatch $pkgname-1.0pre7-gcc4-amd64.patch

So is pacman ready to manage different ports this way. What do you think, is it better to have common pkgbuilds like gentoo, frugalware and all the rpm based distributions? Or better using each port their own one?

cactus · 2005-12-28 00:13:14

for the sake of simplicity, I think it is better to have seperate SCM branches for each architecture.

Better, when the branches are small.. If/when other architectures get "folded into" the main arch development team, I think it would be easier to have architecture specific sections.. although this complicates the pkgbuilds..

I guess I see no easy and/or elegant solutions to this balancing act right now..though..I haven't thought overly much about it. Most of the "top layer" ideas I have in my head just during reading this.. are either messy, or lead to needless duplication.

Arch Linux

#1 2005-12-27 22:50:04

Better multiarch pkgbuilds or each port their own one?

#2 2005-12-28 00:13:14

Re: Better multiarch pkgbuilds or each port their own one?

Board footer