You are not logged in.
Pages: 1
Is there a way I can install or compile these?
Offline
...This is arch. RPMs and DEBs are for Red Hat and Debian, respectively. You should be able to find the packages in the AUR, write pkgbuilds for them, or compile them from source. You could also look at the program "alien".
Offline
You may want to have a look at deb2targz and rpmextract.
Offline
After you convert the deb/rpm with deb2targz/rpmextract, it's just a matter of copying all the files to the right place in the filesystem. The cleanest method would be to write a simple PKGBUILD (consult the wiki).
Last edited by tdy (2009-01-11 03:29:18)
Offline
If you really have to use a deb or rpm file, I recommend making a pacman package which uses the above mentioned tools to extract the files. That way pacman will still be managing your files.
Offline
thanks everyone for your help
Offline
Still, is anyone aware of postinstall, preinstall and other scripts that appear in rpm and deb files? I have to install some packages that are .rpm only, I'll try to map these pre post scripts to pacman functions that might result in PKGBUILD...
I wonder why noone else encounter such a problem, maybe only me is using Lotus Notes (as an example)
Last edited by Kirurgs (2009-01-19 10:13:00)
Offline
Kirugs, I'm looking into doing something similar. I though want to be able to rebuild src rpms on arch linux and using the resulting rpm in the PKGBUILD. I plan to be using the rpm commands directly (a full rpm installed on arch, but the pacman database only used to keep track of what is installed).
In other words I want to create a PKGBUILD for an arch-rpm evironment, and then an easy template to use src rpms as the source in subsequent PKGBUILDs (using rpmbuild --rebuild in the PKGBUILD and then extracting the subsequent rpm and running the pre/post scripts).
Last edited by dschauer (2009-02-05 14:06:47)
Offline
dschauer - is there some advantage in using src rpms, instead of the upstream source code? As I understand your post, you're going from src rpm to binary rpm to Arch package, all inside a PKGBUILD, when you could just go from upstream src to Arch package i.e. like a normal PKGBUILD.
I've never used rpms, so I'm just wondering why you want to do this. If it's the pre/post stuff, the Arch way to do that is with a *.install script.
Offline
tomk: I use a lot of RPMs at work and we build our own RPMs. (I'm in a work environment that primarily uses RPM based distros). I wanted to have a way that cuts down on the time needed to convert SRC RPMs to Arch Packages.
I guess a generic SRC RPM to PKGBUILD translator and then a tweak of the output if need be (different locations in /etc, modified rc start/stop scripts, etc) would be a more appropiate method to facilitate this.
Offline
@dschauer
This may be a stupid question... what is the advantage of using a SRC RPM over normal source?
Offline
@u_no_hu
Not a stupid question. No real advantage, apart from most of the work of the Archlinux PKGBUILD is already in the RPM spec file, just in a different format.
An RPM spec file to PKGBUILD translator is really all I would need to develop. I just think it is reinventing the wheel to have to create a PKBUILD from scratch when someone has already entered in all that information elsewhere.
Offline
Pages: 1