# avfs/cfg - "Build" settings for package #--------------------------------------------------------------------- [technotes] 1. "avfs" is a virtual filesystem project that is very old but still more or less in beta. It should be used with caution. However, it's been maintained and seems to work. #--------------------------------------------------------------------- 2. "avfs" is probably only suitable, except for special cases, for use with small archive files. "avfs" is believed to extract archive contents, at least for some types, to a temporary directory stored on disk or possibly in RAM. So, for large archives, it may be slow and/or may consume a lot of disk space or RAM. For the use case of small archive files, however, it may be quite use- ful. Recent releases of "fusezip" (aka "fuse-zip") might be better in the case of ZIP files. #--------------------------------------------------------------------- 3. Example of use: Assume that the directory "/foo" contains a ZIP file named "bar1.zip" and a tarball named "bar2.tgz". Additionally, assume that "bar3.tar.xz" is another tarball stored in "/some/directory". mountavfs # Initial setup ATOP=$HOME/.avfs cd $ATOP/ # Go to the special $ATOP directory ls -l # Contents of "/" are displayed cd $ATOP/foo/bar1.zip# # Go into the ZIP file ls -l # Contents of ZIP file are displayed cd $ATOP/foo/bar2.tgz# # Go into the tarball ls -l # Contents of tarball are displayed # Go to a no-password FTP site cd $ATOP/#ftp:ftp.funet.fi ls -l # Contents of FTP site are displayed cd /some/directory # Go to an arbitrary directory # Go into a tarball in that directory cd $ATOP/`pwd`/bar3.tar.xz# ls -l # Contents of tarball are displayed In this example, appending "#" to the name of an archive file accessed under $ATOP will simulate a directory tree containing the contents of the archive file. Write access isn't supported under $ATOP. Note: Not to regular direc- tories, regular files, or anything stored inside a simulated archive contents directory. #--------------------------------------------------------------------- 4. In theory, "avfs" supports access to websites. In practice, we haven't been able to make that feature work. Attempts to do so lock up the package. #--------------------------------------------------------------------- [buildtimes] 00.01 hours (or 000.55 minutes) - ThinkPad E540 i7 4x2 16GB RAM 00.01 hours (or 000.63 minutes) - 2021 L.A. dedi box: 6x2 CPU 32GB RAM #--------------------------------------------------------------------- [settings] build = default fortran = disabled license = See "license*.txt" in installed tree licfile = COPYING nls = disabled dontfind = fuse310 setpaths = fuse209 tmpsize = 18M #--------------------------------------------------------------------- [depends] actools fuse209 fuse310 gawk grep libneon perl5:forward pkgconf sed xzutils zstd #--------------------------------------------------------------------- [configure] MANBASE=$PKGDIR_PROD/man mkdir -p $MANBASE autoreconf -fi bash ./configure \ --prefix=$PKGDIR_PROD \ --build=$LACARCHBUILD \ --host=$LACARCHHOST \ --disable-dependency-tracking \ --enable-fuse=yes \ --enable-shared=yes \ --enable-static=no \ --mandir=$MANBASE #--------------------------------------------------------------------- [postbuild] cd scripts chmod 755 *mountavfs cp -p *mountavfs $PKGDIR_PROD/bin/ #--------------------------------------------------------------------- # Original URLs. These URLs were valid at one point, but may have died # since then. If you download newer versions of tarballs [etc.], don't # delete the original versions, as you may not be able to replace # them. [urls] url_debian = tbd url_home = tbd url_lfs = tbd url_tarball = https://downloads.sourceforge.net/avf/avfs-1.1.5.tar.bz2 #--------------------------------------------------------------------- [history] 190812 Added package. Started with 1.1.1. 210126 Updated to 1.1.3 210423 Updated to 1.1.4 230218 Updated to 1.1.5