2008/9/23 Aaron Griffin <[EMAIL PROTECTED]>: > On Sun, Sep 21, 2008 at 7:16 AM, Roman Kyrylych > <[EMAIL PROTECTED]> wrote: >> Hi all! >> >> Got to chrooting today, to get my packaging process correct. >> Here's what I've got: >> >> [EMAIL PROTECTED] ~]# echo $CHROOT_SHELL >> /chroot64 >> [EMAIL PROTECTED] ~]# mkarchroot $CHROOT_SHELL/root base base-devel sudo >> mounting sysfs : /sys >> mounting procfs : /proc >> binding device nodes : /dev >> binding pacman cache : /var/cache/pacman >> installing packages: >> base >> base-devel >> sudo >> Root : /chroot64/root/ >> Conf File : /etc/pacman.conf >> DB Path : /chroot64/root//var/lib/pacman/ >> Cache Dirs: /var/cache/pacman/pkg/ >> Lock File : /chroot64/root//var/lib/pacman/db.lck >> Log File : /chroot64/root//var/log/pacman.log >> Targets : base base-devel sudo >> >> Notice the // >> I've looked into the source, but haven't found what causes / to appear >> after /chroot64/root > > Does this cause any issues? Or is it just cosmetic? >
It doesn't cause issues, I've successfully built a package that required many (make)depends in that chroot, so double slashes seem to had no effect on chrooted pacman's paths. So it just cosmetics, but it's weird that I couldn't found what causes it. -- Roman Kyrylych (Роман Кирилич)
