Offline installation of packages. This is a simple way to install a package. Generate a list of packages to download. This can be done on any Arch Linux. 'How to install package.deb in Archlinux'. Ok, first you must install package dpkg from AUR Archlinux. Tip: Be aware you have enabled at least one of the servers defined in the /etc/pacman.d/mirrorlist file. Otherwise all what you get is a misleading error message: error: no database for package: package-name. To update a New Arch Linux base system after installation you may enter # pacman -Sup --noconfirm > pkglist Now open that textfile with an editor and delete all lines that are not URLs. Next, bring that list with you to a place where you have internet and either download the listed packages manually or run wget in an empty directory: # wget -nv -i./pkglist. Tip: When using or some other kind of Windows environment to download the packages the filenames will get mangled, since default Windows file naming requires to escape e.g. To avoid this (under cygwin, since it doesn't follow such restrictions) use wget --restrict-file-names=unix. Take all the *.pkg.tar.gz files back home, put them in /var/cache/pacman/pkg and finally run # pacman -S package-name A simple example This is a simple way to install a package you have downloaded: # pacman -U /root/Download/packagename.tar.gz This is how to install several packages you have installed into a directory # pacman -U /root/Download/*.tar.gz A slightly contrived example Scenario: you have two Arch Linux machines, 'Al' (with internet connection) and 'Bob' (without internet connection), and you need to install some packages and their dependencies on 'Bob'. Jasonwryan (as per usual) was right on the mark with his initial comment. Arch's packages are supposed to be as close to 'vanilla' as possible. Now, while you could use rpmextract or alien, there isn't really a good reason to do so. What you should do is create a PKGBUILD that uses the RPM as the source file and then installs everything that's needed where it should be in the package() function. If you are unsure of how to do this, take a look at some packages on the; there are plenty that do similar things. Now, since bsdtar (the default extractor used on source files by makepkg) supports extracting RPMs without issue, there is no reason to use rpmextract—it adds a makedependency without adding any real functionality. Some related reading from the wiki: • • •. There's a tool called alien that can (attempt) to build a deb from the rpm.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |