On 23/06/10 11:55, Baho Utot wrote:
On 06/22/10 19:31, Allan McRae 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
What about SRCDEST ?
Creating a sym link from source package to the build directory would be
handy as well.
Do you mean SRCDEST or SRCPKGDEST. The first should already work, the
second has a patch on the pacman mailing list.
Allan
