[maemo-developers] MeeGo
From: Michal Kolodziejczyk miko at wp.plDate: Tue Feb 16 12:06:48 EET 2010
- Previous message: MeeGo
- Next message: Porting Yum to N900?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 16.02.2010 08:44, Martin Grimme wrote: > I think this is the real problem about rpm here. Technically, I think > rpm is superior to deb but Debian's apt is still unmatched as a > package manager and the packagers do a better job (maybe because deb > is easier to create?). I haven't used yum for years, so it might be > better today, but back then (2004/2005), badly packaged stuff with bad > dependencies and the utter slowness of yum drove me away from Redhat. Mee too ;( BTW, I am using archlinux now and its pacman package manager - it it simply beatiful compared to rpm/deb - you can create new packages usually in "no-time". For me, both deb and rpm are "poisoned" by using macros: they have similar names but different implementations across linux distributions, or they are present in one distro and not in the other, and this is the worst problem of RPM (and also deb, I suspect). I was creating deb and rpm packages long time ago, but now knowing pacman and the current state of deb/rpm packages, it is really hard to go back :( > I was involved in a project creating a Linux LiveCD builder based on > Fedora for customer-customisable CDs. The user selects the > applications she wants on the CD and the CD builder automatically > resolves the package dependencies to build the CD. While in theory This is what "just works" with pacman - see http://larch.berlios.de/doc/larch_overview.html I know the rpm path is already decided, just wanted to point at an alternative simpler solution which just works. Regards, miko
- Previous message: MeeGo
- Next message: Porting Yum to N900?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]