Hi list
Jakob and I have been going back and forth about where groups handlings should
be, in backend or frontend, and how alpm interface should look like.
It turns out Jakob has several arguments for the group backend solution, and he
spent quite some time working on it, improving and fixing
Xavier wrote:
Hi list
Jakob and I have been going back and forth about where groups handlings should
be, in backend or frontend, and how alpm interface should look like.
It turns out Jakob has several arguments for the group backend solution, and
he
spent quite some time working on it,
On 01/10/10 01:29, Xavier wrote:
Allan McRae wrote:
No. It also affects the location of the tarfile. e.g. PKGDEST=.
puts the tar file in $pkgdir because we create the tarball location
using $PKGDEST while in $pkgdir:
cd $pkgdir
...
Jakob Gruber wrote:
The repo name ( = db name) is passed to the 'Install whole content
from ...' callback but not to 'group :: Members: pkg1 pkg2'.
This results in the following output: http://pastebin.com/LpG0MKSc
This is a little inconsistent, but it's still clear what's going on
IMO.
On 04/10/10 13:46, Allan McRae wrote:
Jakob Gruber wrote:
The repo name ( = db name) is passed to the 'Install whole content
from ...' callback but not to 'group :: Members: pkg1 pkg2'.
This results in the following output: http://pastebin.com/LpG0MKSc
This is a little inconsistent, but
This prevents circular symlinks and weird final package locations
when using commands like 'PKGDEST=. makepkg'.
Fixes FS#20922.
Signed-off-by: Allan McRae al...@archlinux.org
---
scripts/makepkg.sh.in | 21 +
1 files changed, 17 insertions(+), 4 deletions(-)
diff --git
