Originally Posted by Drakeo
I really like the multilibpkg I just wish it did not put so many folders in my /tmp I wish it put it in the /tmp/multi I will have to change some codes I will have to change some codes.
same problem with massconvert32.sh
By default, multilibpkg
to store downloaded packages, uses /var/lib/multilibpkg
as working directory, but, it (should) not put anything into folder /tmp
. Cache and working directories can be changed by altering the variables MULTILIBPKG_CACHE
into the configuration script /etc/multilibpkg/multilibpkg.conf
In the case of compat32pkg
, this uses /var/cache/compat32pkg/slackware-32
to store downloaded packages, uses /var/cache/compat32pkg/compat-32
to store packages to format compat32 produced by convertpkg-compat32
, and uses /var/lib/compat32pkg
as working directory. These caches and working directory can be changed by altering the variables COMPAT32PKG_CACHE
into the configuration script /etc/compat32pkg/compat32pkg.conf
. The "too many folders" into your /tmp
come from convertpkg-compat32
when used explicitly or implicitly when using compat32pkg or massconvert32.sh. However, convertpkg-compat32
allows you to change this using its environment variable TMP
. Therefore, what you wish can be done like below :
1. when using convertpkg-compat32 explicitly
$ TMP=/tmp/multi convertpkg-compat32 ...
2. when using convertpkg-compat32 through massconvert32.sh
$ TMP=/tmp/multi massconvert32.sh
3. when using convertpkg-compat32 through compat32pkg
$ TMP=/tmp/multi compat32pkg ...
I guess it should be a good idea to add a variable into configuration's script for compat32pkg
to manage that. This could be something like CONVCOMPAT32_TMP
which will be set to /tmp/compat32-packages
by default. What do you think about that ?