You are not logged in.
http://www.mediafire.com/ShadowKyogre
Has a bunch of micellaneous stuff...but most of it are my custom .pkg.tar.gzs for Arch Linux. Enjoy!
Want a conversion request? Post it here!
Last edited by ShadowKyogre (2009-01-22 03:26:36)
For every problem, there is a solution that is:
Clean
Simple and most of all...wrong!
Github page
Offline
I don't understand why you would want to do this... especially for boost?
Could you add the versions so people know what is going on with them? In fact, how did you make those packages because it was not with makepkg.
Offline
Well, that was for memory purposes since I wanted to keep an svn version of boost using Xyene's PKGBUILD (1.3.7). Anyway, I made the packages by placing them in the correct install paths, writing PKGINFOs on them, and tarring them up. I have a tut here:
http://wiki.archlinux.org/index.php/User:ShadowKyogre
Plus it's much more simple for me than compiling from source.
And yeah...I'll need to do that sometime like a weekend or something.
Last edited by ShadowKyogre (2009-01-22 03:41:24)
For every problem, there is a solution that is:
Clean
Simple and most of all...wrong!
Github page
Offline
My point was, if you write a PKGBUILD where you do the extraction of the deb/rpm and install them to the right place, makepkg will do all the .PKGINFO creation etc for you. I'm sure there are examples of this in the AUR...
Offline
Yeah...but apparently I didn't write up PKGBUILDs. Probably I should learn how to make those too.
For every problem, there is a solution that is:
Clean
Simple and most of all...wrong!
Github page
Offline
I'd rather rebuild the packages from source anyways myself. See this forum post: http://bbs.archlinux.org/viewtopic.php? … 72#p493672
Offline
Yeah...but apparently I didn't write up PKGBUILDs. Probably I should learn how to make those too.
yeah, i'd say. arch already includes two or three good implementations of the wheel. manually writing .PKGINFOs for .debs and .rpms seems like re-inventing it yet again, but adding corners.
[23:00:16] dr_kludge | i want to invent an olfactory human-computer interface, integrate it into the web standards, then produce my own forked browser.
[23:00:32] dr_kludge | can you guess what i'd call it?
[23:01:16] dr_kludge | nosilla.
[23:01:32] dr_kludge | i really should be going to bed. i'm giggling madly about that.
Offline
I usually use deb2targz and then extract the contents to where they should go, but obviously in a PKGBUILD so things are easier. Check my crossover packages:
http://aur.archlinux.org/packages.php?SeB=m&K=LTSmash
Any will do
Proud Ex-Arch user.
Still an ArchLinux lover though.
Currently on Kubuntu 9.10
Offline
What would be the mileage in a debs converter ie convert a native ubuntu package to Arch?
Mr Green I like Landuke!
Offline
I have a tut here:
http://wiki.archlinux.org/index.php/User:ShadowKyogrePlus it's much more simple for me than compiling from source.
For the sake of the Arch community, I sincerely hope that you are the only one who thinks your process is simpler than writing a PKGBUILD and using makepkg.
IMO there is only one sane reason for using rpms/debs on Arch, and that's for applications which are only distributed in that format, and for which the upstream source is unavailable.
Mr Green - I think you'd be lucky to get "inchage" out of a deb/rpm2Arch converter, let alone mileage.
Offline
For the sake of the Arch community, I sincerely hope that you are the only one who thinks your process is simpler than writing a PKGBUILD and using makepkg.
I would just like and automated translation from a source rpm (or deb) to a PKBUILD and surrounding files that I could tweak as need be. (Since no translation tool seems exist I'm considering writing my own).
As far as the rest of this discussion goes, while I'm not trying to offend anyone, the idea of using a package that was built on some other distro to a binary rpm or deb and then converted as is to a binary package for ArchLinux is a bit distateful to me. One should always be able to use makepkg to rebuild a package that matches the current installed libraries, etc, and where all the files are properly tracked by pacman.
Offline
ShadowKyogre wrote:I have a tut here:
http://wiki.archlinux.org/index.php/User:ShadowKyogrePlus it's much more simple for me than compiling from source.
For the sake of the Arch community, I sincerely hope that you are the only one who thinks your process is simpler than writing a PKGBUILD and using makepkg.
I could not agree more. For a distro that is centered around knowledge and users that have to do a fair bit of DIY, this kind of things is imho not done. It's fine if you choose to do this for your own system, but please don't promote it. You shouldn't be breaking other people's installations. A PKGBUILD in AUR is a far more valued contribution than a converted .deb or .rpm (although the community values any contribution of course ).
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline