On Tue, Jun 22, 2010 at 10:48 PM, Allan McRae <allan@xxxxxxxxxxxxx> wrote: > On 23/06/10 10:47, Ng Oon-Ee wrote: >> >> On Wed, Jun 23, 2010 at 7:31 AM, Allan McRae<allan@xxxxxxxxxxxxx> wrote: >>> >>> On 23/06/10 07:01, Attila wrote: >>>> >>>> Hello together, >>>> >>>> since the new pacman a makepkg run creates a symlink to the package file >>>> in the >>>> directory of the PKGBUILD. Example: >>>> >>>> # ls -l *.gz >>>> opera-snapshot-10.60-6378.2ah-i686.pkg.tar.gz -> >>>> >>>> /server/work/archlinux/repo/opera-snapshot-10.60-6378.2ah-i686.pkg.tar.gz >>>> >>>> My differences to makepkg.conf.pacnew be this: >>>> >>>> MAKEFLAGS="-j2" >>>> CFLAGS="-march=i686 -mtune=generic -O2 -pipe -fomit-frame-pointer" >>>> CXXFLAGS="-march=i686 -mtune=generic -O2 -pipe -fomit-frame-pointer" >>>> BUILDENV=(fakeroot !distcc !color !ccache) >>>> OPTIONS=(strip !docs libtool emptydirs zipman purge) >>>> PKGDEST=/server/work/archlinux/repo >>>> PACKAGER="Attila<SysAdmin@hunnen>" >>>> PKGEXT='.pkg.tar.gz' >>>> >>>> [/server/work is a cifs mount point] >>>> >>>> Have i overseen something in the makepkg.conf to control this or does no >>>> one >>>> have this problem ... or is this a new feature which have to be so? >>> >>> New feature. If PKGDEST is set, it creates a symbolic link to the >>> packages >>> in the working directory. I think the idea was that most of the time you >>> will want to "pacman -U<pkg>" at the end of the build and that save you >>> typing the whole PKGDEST path. >>> >>> Allan >> >> Wouldn't those who want to do that do a makepkg -i? The thing about >> leaving a symbolic link is that the next time you do pacman -Sc its >> still there. Scripting removal of dead links is dead simple though, so >> not a problem for me. >> > > Possibly... I do not use "makepkg -i" as I use "makepkg -sr" so it removed > the makedepends that will be unneeded in the future. Using "makepkg -c" > clean up the dangling symlinks. It is also a very helpful symlink for those of us that like to run namcap after building to check the package. -Dan