URPMI For Fedora Core 2 246
Jaroslaw Zachwieja writes "Stefan van der Eijk, the autor of Slbd - automated tool to rebuild distributions to different architectures/processors in a sanitized environment, has published set of RPMS of URPMI for Fedora Core 2. The only usage difference is that it uses hdlist instead of compressed hdlist.cz known from Mandrake. Are we one step further towards Cross-distro RPMS?"
apt (Score:2, Insightful)
URPMI does depndancy resolution (Score:5, Informative)
URPMI can do pretty much everything apt can do. It is really no better or worse. Apt has more conveient commands for some things, URPMI does for others.
Same shit, different stick really.
Re:apt (Score:2)
Re:apt (Score:2, Insightful)
If RedHat or SuSE were to have the same army of developers managing packages and ensuring their dependencies are all assigned correctly, they'd be just as effective as Debian.
Re:apt (Score:2, Insightful)
Re:apt (Score:2)
Still, I sigh each time a new RPM-based distro or tool is announced. Why couldn't they just adopt Debian's packaging tools? They were there first, and worked well from the beginning. RPM has been a nightmare.
dpkg !> rpm (Score:3)
There is nothing to be gained from using dpkg over rpm, really. I'm a debian user, and in fact would prefer if Debian switched over to rpm (which is specified in LSB as the standard packaging mechanism, BTW). Dependency resolution and all that works with rpm as well.
Obviously this will happen, because Debian is, well, Debian.
Re:dpkg ! rpm (Score:2)
Debian packages don't suffer from the incompatibilities that RPMs do (RPM was changed incompatibly a number of times), and RPM has long lacked the convenience of apt. All this could have been avoided if distros had adopted
Re:dpkg ! rpm (Score:2)
Why don't you detest Debian instead for sticking to a format that is not the "standard" as specified by LSB, esp. if there are no real technical reasons? Why not go for a format that is being backed by hard corporate money?
Re:dpkg ! rpm (Score:2)
In what world is that? There is apt for rpm my friend and some HUGE repositories out there.
Yes apt is good and wonderful, deb is equal, so why not drop deb like the rest of the distros out there and keep apt?
Right now debian is not standards compliant, like the parent said rpm is specified in the LSB. This fight was fought and settled long ago... debian just won't listen.
Re:apt (Score:3, Informative)
One final argument is that
Re:apt (Score:5, Informative)
APT is a great management tool. But it is not a packaging format/tool.
APT already works with Debian, debian dkpg based distros and some RPM based distros as:
- Conectiva (they ported to rpm and support apt use)
- Mandrake (at least for the cooker)
- Redhat and Suse (thru 3rd party prepared mirrors)
An advantage of URPMI over APT is that URPMI can do small updates instead of taking the
whole package list and putting it in a big "rpm -Uvh" command line.
Re:apt (Score:2, Interesting)
- Chroot support (configurable with an option like --root);
- Media support (configurable with an option like --media cooker_main,cooker_contrib). With yum and apt it seems to be possible, but then you need to point them at a different configuration file;
- Speed. On my Fedora box urpmi is *much* faster than yum. Yum seems to nee
Re:apt (Score:2, Funny)
urpmi vs yum (Score:5, Insightful)
Re:urpmi vs yum (Score:5, Informative)
1. urpmi.addmedia -- allows a user to define new media (cdrom, ftp, nfs, etc) to be used for getting updated rpms and dependencies. Graphical tool is gurpmi.addmedia.
2. urpmi.update -- polls the media sources that are not on fixed media and downloads fresh hdlist files if available.
3. urpmi.removemedia -- samey same as addmedia, only in reverse. No graphical tool as this function is available in guprmi.addmedia utility.
4. urpmi / gurpmi -- command line / graphical utilities to download/install new/updated rpms, solving dependencies along the way.
5. edit-urpm-sources.pl -- a GUI tool available for Mandrake to edit the list of available source media.
I keep hearing about yum, apt, red-carpet, etc, and read a lot of confusion about how they compare to Mandrake's tool. I've messed with Debian's apt/get system on my testbed machine, but I keep coming back to Mandrake and urpmi. It's familiar, easy to use and I likes it.
Re:urpmi vs yum (Score:2, Informative)
Re:urpmi vs yum (Score:5, Interesting)
Re:urpmi vs yum (Score:2)
Honestly, both points seem rather trivial to me. My experience with yum suggests maximum dependency resolution time of 15 seconds, which is not that big a deal considering that you don't do that too often - and the packages need to be fetched anyway.
Re:urpmi vs yum (Score:3, Funny)
If you like what you ate, you say, "Yum!", otherwise you involuntarily make a noise like, "urpmi".
No need (Score:4, Informative)
alien works perfectly well for importing rpms and solaris packages... never failed on me.
(Although in some cases a little directory tweaking might be necessary, but that`s really not that much of an issue, at least IMHO)
Re:No need (Score:5, Funny)
* Your 2.0.x Debian kernel notwithstanding...
Great! (Score:2)
Sure, it's not really a problem using DAG or some other repository, apt, yum etc, but urpmi is at another level (at least for mandrake).
Re:Great! (Score:5, Funny)
So you don't miss your boot sector?
*drumroll*
Sure, it's not really a problem using DAG or some other repository, apt, yum etc, but urpmi is at another level (at least for mandrake).
Isn't that mostly an issue with available repositories, as opposed to software that does the fetching and installing?
Yes please. (Score:5, Interesting)
I was introduced to chroots not to long ago and this made my life a little more simple. Just create a small partition of your disk, install a distribution there, don't update the boot partition and move the new dist to a directory on your system. Then just cd into that dir and chroot. Whammo, instant mandrake/suse/redhat/fedora. =)
Atleast for devel purposes.
I don't know much about windows but I imagine that this is one thing that they've managed to nail down. Something created on XP have a fair chance of running on other windows. Or am I misinformed?
Re:Yes please. (Score:3, Informative)
Usermode Linux will get you an even more complete experience. This is what we use at emperor linux [emperorlinux.com]
to keep our distribution images up to date, all running on one big quad-xeon server.
The main strength of this is that your fake fedora/suse/whatever machine has its own process list and
Re:Yes please. (Score:3, Interesting)
Of course, you could enforce standards so tightly that there's only one implementation (yours). The real art is to create a standard flexible enough that I can do what I want (need) to without "breaking" your standard.
Mabye you don't want stuff in
The lost Newbie blinks... (Score:5, Interesting)
I think I speak for all long term windows users here when I say.... Huh?
I've only got the faintest idea what this article is going on about, but since I'm a Fedora user with a gripe about installing software on linux, I'll brashly comment anyway.
RPM is good. I love RPM. I can't imagine where I'd be without that lovely self contained, self extracting package that Just Works(TM). Of course sometimes it dosen't Just Work, like when it was built for a different distro, which is very annoying.
Still, it's either that or configure,make,make install or a big gcc -lSDL - lSDL_image -lGLU etc..... for about 50 files. And while these things aren't rocket science, not having a double click to install makes my Linux life all the harder. I'm too long in the windows universe perhaps, but I still like RPM. Now if only it had a GUI.
But on the other hand, will self installers lead us down the path of mindless users, spyware and spam boxes with
embedded linux(the horror)!!! Do we tread the path of usability at our peril?
P.S.
What's hdlist.
Re:The lost Newbie blinks... (Score:2)
Re:The lost Newbie blinks... (Score:2)
Just about every Linux distro except Fedora has a standard graphical installer. If that is important to you, I think you may have chosen the wrong distro.
But if you decide to use Fedora anyway, you should be using yum, which is a layer on top of rpm that automatically resolves dependencies. yum is much easier to use than rpm.
Re:The lost Newbie blinks... (Score:2)
Um
Re:Debian (Score:5, Insightful)
Yes, people keep repeating this nonsense in every Slashdot discussion about packages and dependency resolution in Linux.
I'll take this slowly. There is a problem, a serious problem, that affects many people. It's that software which is not in the distros repositories is too hard to install.
The solution is not "just use Debian because that has everything". Firstly, not all software is in Debian, and some never will be - proprietary software that does not have Debian packages and cannot be repackaged, for instance. Secondly, not everybody wants to use Debian.
Some people like the graphical installers, branded graphics, fast release cycles and tightly integrated desktops that distros like Fedora, Mandrake and SuSE provide. Even if Debian provided all these things are more, there would still be non-Debian distros that people wanted to use. Debian has had years in which to wipe out the competition with its superiority, it has not happened and probably will not.
Even if Debian was the only Linux distribution anybody used, it would still not be a "solution".
Both in unstable and - yes! even in experimental - distro packages are frequently out of date or wrong. The Wine and Mono packages have this problem for instance. For Wine Gentoo is a particularly bad offender. It routinely causes a support nightmare.
They are out of date or wrong because the traditional Debian orthodoxy that centralised packaging works best is also wrong. Think about that for a moment.
I'm sure you're dying to tell me why I'm wrong, why Debian/Gentoo packagers with a guru-like understanding of Debian/Gentoo policy will always do a better job than a hapless developer, and why having all the packages in a central place allows for better "integration".
I'm not going to name names, but I have seen far, far too many flat out broken packages that are excellently integrated with their distribution but are nonetheless wrong. In some cases, they would not even start. I'm thinking primarily of Wine here because that's what I know. Wine is not exactly difficult to install, especially not in the latest versions yet somehow people still get it horribly wrong. I know from talking to other developers though that once you bring up this taboo topic, all kinds of horror stories come out of the woodwork. Brokenness on Debian, on Gentoo, on Mandrake, on Fedora ... the list goes on and on.
Mistakes include not shipping critical files, shipping them in separate "optional" packages when they aren't optional at all, shipping the right files but putting them in the wrong places so the app can't find them, incorrect modifications to system settings based on flawed understanding on the behalf of the packager, oh and the worst - applying random patches which either aren't sent upstream or are so hacky and/or incorrect that they're rejected but still applied downstream.
All these problems cause support nightmares for the developers who at the end of the day actually know how to install their software. Projects don't outsource documentation writing, or usability, or optimization, why should installation be any different?
The Debian approach has many other problems. It doesn't scale. Keeping all the packages up to date requires horrific amounts of manpower and these distros still have problems doing releases. The problem affects every distro: a few days ago I installed Gimp into Fedora and found that it was a 1.3.x prerelease package! Gimp 2 has been out for ages now, and it's still out of date. Desktop Debian basically does not release, you have to use unstable to get a modern system and risk occasionally being locked out of your own system (eg, pam problems) and the like, and Gentoo has given up on that entirely and simply marks a snapshot 4 times a year as their "release".
The right solution to this problem - for eve
Re:Debian (Score:2)
Your solution, developers packaging for every distribution, is not going to work unless this is made ridiculously easy. I don't think this is ever going to happen. I have tried packaging software for various distros, and I found it to be a complex and laborious process.
Re:Debian (Score:2)
Well, I disagree [autopackage.org]. I'm working on making it easy. So far it's not doing badly, though for more robust installs we want to be able to delegate to apt/yum/urpmi/whatever when there are no distro-neutral packages available.
I am the Debian zealot I am because many people complain that something does not work in "Linux", even though it does on Deb
Apples and oranges (Score:2)
I don't have a response to the amount of packages available, except to say that I created a mini yum-repo on my own box - just a directory that yum knows to access - of everything I couldn't find in a standard repo.
The rest of your post is just Distro Wars, and largely irrelevant. The grandparent didn't say anything about Debian, and you can get apt-get for F
Re:Debian (Score:2)
Debian currently has > 13,000 packages, and no Mandrake of Fedore wil ever top that. That is why apt is so cool
Re:The lost Newbie blinks... (Score:4, Insightful)
RPM Lacks Security Checks (Score:4, Interesting)
The RPM system has virtually no assurance of GPG key identification. Basically, if a mirror (or any website that serves RPMs) pushes out malicious RPMs, the GPG check by the RPM installer gives NO warning if the RPM isn't encoded at all, and only a passing warning if it doesn't match the RH public key.
This is a potentially huge hole in all RPM based distros, as was demonstrated to me recently by a manipulated RH RPM which, when installed, deleted the iptables rules file and various other things. Yet, the RPM system barely complained about the GPG mismatch and installed anyway (without telling what it did either).
If we're moving toward cross-distro RPM system, it is multiplying the potential problem. I think this needs to be addressed before such a system is adopted by other distros.
Re:RPM Lacks Security Checks (Score:5, Informative)
If warns you (and requires a confirmation to continue) if a package is not signed. It warns you (and requires a confirmation to continue) if a package is signed, but you have not told urpmi to trust packages signed by the key used for the packages in the repository you are using.
That's another advantage urpmi has over all other packaging frontends I am aware of.
Re:RPM Lacks Security Checks (Score:2)
Re:RPM Lacks Security Checks (Score:3, Informative)
Re:RPM Lacks Security Checks (Score:2)
I call bullshit. urpmi has been doing just this kind of checking f
Re:RPM Lacks Security Checks (Score:2)
I should correct myself here. That's zarb.org [zarb.org], and the the Penguin Liberation Front [zarb.org].
Re:RPM Lacks Security Checks (Score:2)
Re:RPM Lacks Security Checks (Score:2)
If you don't bother to use --checksig, then you've got a lot of security home work to do. I doubt that RedHat rolled such a package, checksig will allow you to verify the source of your packages (at the cost of collecting a few (trusted) public keys).
Query the package for a correct signature before installation, like so:
rpm -qp --checksig package.rpm
If there's no signature, or it's not a valid one, don't run the installation command.
Kitchen knives are used to cut. If you slice
Both urpmi and yum support gpg checking (Score:2)
In yum.conf add gpgcheck=1 and it will check that the GPG signature.
urpmi is set to check signatures by default and normally a repository will tell you what sigs its RPMs are signed with when you add it.
The difference is GUI (Score:3, Interesting)
Re:The difference is GUI (Score:5, Informative)
Re:The difference is GUI (Score:2, Insightful)
Re:The difference is GUI (Score:2)
Really? I wonder how I managed to install new packages with up2date then. Must have been some odd bug or something that let me do it by accident.
Jedidiah.
Re:The difference is GUI (Score:2)
Re:The difference is GUI (Score:2)
Re:The difference is GUI (Score:2)
Yay, more out of sync updaters (Score:4, Insightful)
Re:Yay, more out of sync updaters (Score:5, Informative)
Different Issues (Score:4, Interesting)
The other issue, the one about being able to write source RPMS (.src.rpm files) that work in several distros, has to do with the different distros standarizing on the RPM macros, file naming conventions, version schemes and so on. It is all in the Back End. It would be great of course, and it would save a lot of duplicated efforts for the different distributions.
What would be even more interesting as a further step, would be to be able to massively build source RPMS from the RPM front end (be it URPMI or whatever), a la gentoo. This is, to provide a systematic way to get the RPM front end to download and build all the SRC RPMS you need to install the package you need (assuming you can't install these dependendencies from binaries). This would help users compile packages from other distros or from third parties in a painless way.
Re:Different Issues (Score:2)
Little-used advantage of RPMs? (Score:2, Interesting)
Re:Little-used advantage of RPMs? (Score:3, Interesting)
Great news, but y'all will need this... (Score:3, Informative)
However, to make urpmi truly useful, there needs to be a repository of good source trees for ftp download for the particular distribution. Thus the folks at zarb.org [zarb.org] created easyurpmi.org [easyurpmi.org] to help folks out in configuring source media on Mandrake. Loaded with lots of different mirrors carrying Mandrake RPMS from the various different sources (main, contrib, updates, plf, etc), this tool generates a commandline that will add a urpmi source media entry to the urpmi database.
Now, someone needs to get on the stick and start compiling the sources for Fedora urpmi sources. Hop to it, kids.
Building from source? (Score:2)
Alternatively, is there a distribution point for AMD (32 and 64 bit) optimized RPMs?
TIA...
Zero Install (Score:3, Interesting)
No more keeping lists of available packages on your local system, or worse, manually tracking dependencies. No more packages not being available for your distro. No more compiling from source. Instead, click and you've got it. I couldn't think of a more user friendly way to install software.
The other great advantage is that it integrates well with both the Web and the local system. With Zero Install you can click and run programs like Java applets, but they will _really_ integrate with your desktop, and _really_ run at native speed. Now hopefully we can kick some bloat out of applications so that they don't take a day to download.
Re:Zero Install (Score:2)
Re:Zero Install (Score:2)
#!/bin/sh
[ -x `which python` ] && exec python prog.py "$@"
exec 0run "python.org/python 2004-01-01" prog.py "$@"
This runs 'prog.py' using the local version of python if available, or using 0install if not (assuming python was avai
Re:Zero Install (Score:2)
For file associations, I'm talking about "run random 3rd party app, save a file, click the file". How does the desktop know to link that file type to the program just run? Maybe ROX knows, how about KDE and GNOME which are based on the idea of files in magic path locations to describe this?
Re:Zero Install (Score:2)
Well, you're the linker expert, but can't something like your relaytool do that automatically? Assuming this is the behaviour you want; it doesn't do much harm to always use the zero install version and phase out use of the old libraries, at least for smaller ones like expat. Using local libraries is a small efficiency gain when running on legacy
Re:Zero Install (Score:2)
relaytool is a useful program to have in our kit, but it's not meant for relaying large numbers of large libraries as is typical with most programs. The relay blocks it generates bloats the working set considerably: while for <100 functions this isn't really a problem once you go beyond that it begins to make an impact.
I think it's possible to use even more advanced linker tricks than relaytool to fix that
Re:Zero Install (Score:2)
I think it's possible to use even more advanced linker tricks than relaytool to fix that problem, by allowing MacOS X style library "swallowing" where the swallowed library is sucked into the executable binary itself and used only if the system library is not present, otherwise the highest version takes priority. But, this is still theoretical and would need more R&D which I don't have time to do currently.
Actually, there
Re:Zero Install (Score:2)
It also doesn't let you choose between newer/older versions, but I doubt that's often a problem.
The trick then for you is to get zero install bundled by default, have you considered sending it upstream to lkml?
urpmi media and Mandrake upgrades (Score:3, Informative)
When upgrading Mandrake, e.g. from 9.1 to 10.0, make sure you delete the old hdlist.cz and synthesis.* files from the previous release, and use urpmi.addmedia to add the new release media (CD) to your machine.
Here is a list of commands to do that:
After that, you can go ahead and add whatever ftp site you want in addition to what you have.
Doing this will save you a lot of confusion and error messages.
This seems wrong (Score:2)
Re:This seems wrong (Score:2)
Bottom line is however that Fedora comes with only yum and it will continue to do so, and up2date also uses yum in the background. New users will just stick with it, if you're experienced enough to have a different preference you can go and download it youself, or use yum to do it for you in the case of for example apt-get from Fedora Extras.
Hurray for urpmi (Score:2)
Why?
*It's dependency handling is superb.
*Urpmi has been honed for a long, long time, longer than apt-for-rpm or yum.
*It makes it dead easy to do parallel installation to a bunch of systems from one master one.
*It is much more efficient than yum. And Yast is a pain if you want to install software from a bunch of external repositories. So long as you stay with what's on the CDs, you are good. Addit
Cross-distro packages is what I need (Score:2, Interesting)
But what I want is cross-distro packages. That would be really useful: how many times I needed that package from kde-apps.org, but I could not install it because it was only available for SuSe and Mandrake and not for Fedora!!!
Well, actually I could install it if I was a serious hacker (take the scr package and hack it so that it works on Fedora), but I am not.
Cross-distro would be very useful for developers too. Supply just
Re:Who needs em? (Score:5, Insightful)
Seriously, is:
make
make install
Really that hard that we need cross distro RPMS?
configure; make; make install does nothing with dependencies. If you, for example, don't have qt development headers on your machine, it just croaks.
Re:Who needs em? (Score:3, Interesting)
configure; make; make install does nothing with dependencies. If you, for example, don't have qt development headers on your machine, it just croaks.
True. I'm amazed that Portage isn't ported to RPM-based distros yet. It handles compiling source gracefully, including dependencies. It can also install binary packages. To me, it's the perfect tool for the job.
Re:Who needs em? (Score:2)
Yes, but the hadnling is automatic these days with software like you and apt-rpm.
I guess you'll have to experience "yum install kde" and see it fetch a zillion packaged to appreciate the work it does for you.
Re:Who needs em? (Score:2)
Oh. As if that's not easy with urpmi??
urpmi.update -a (updates all media sources)
urpmi kde (grabs latest kde with dependencies)
samey same
Re:Who needs em? (Score:3, Insightful)
Comparison was with configure/make/make install, not urpmi.
Re:Who needs em? (Score:2)
Now if gentoo only had a simpler way to install everything... (but they do have a nice upgrade path!)
Re:Who needs em? (Score:2)
Re:Who needs em? (Score:5, Insightful)
And besides, if it makes my life even a little easier, I'll be pleased.
Re:Who needs em? (Score:3, Insightful)
The last thing we should want to see is an Install Wizard on Linux. The software should be smart enough to install itself, without any help on my part (unless I want something special, like a different install directory, or some such). We're almost there with apt-rpm-autopackage. Dependecy resolution is the tough nut to crack for all distros.
Why do people think that Install Wizards are so easy? For someone who has never installed software (or, used a computer beyond checking email,
Re:Who needs em? (Score:3, Interesting)
Because they are time saving. The mac handles installs very poorly for instance. One click is a beautiful dream but not worthwhile in practice. Even intermediate users want to change options alot of the time.
What is poor is your installation class choices. With linux we don't have to care about sounding professional like commercial offerings.
A few sample possibilities:
"I Intimidated, figure all this out for me."
Picking this and clicking next wi
Re:Who needs em? (Score:5, Interesting)
Last time I compiled just the kde-base it took over 12 hours. When a RPM would do the trick in less then 5 minutes. Sure, you may lose some of your precious 'performance tweaks' but you didn't have to wait a day to use it!
BTW, I use Gentoo and love it so I'm not some corporate brainwashed RPM troll. But I can see the benifits of RPMs in a more 'commercial' environment.
Re:Who needs em? (Score:2)
Re:Who needs em? (Score:2)
Re:Who needs em? (Score:5, Insightful)
make
make install
Really that hard that we need cross distro RPMS?''
I hope you don't really think so.
First off, autoconf configure scripts take a long time to run, and if the package is of any complexity, the compilation will also take a long time.
Secondly, all sorts of things go wrong during
Third, make install is typically run as root. Do you trust the script not to install any trojans? How about
Fourth, software built and installed from source can be a bitch to uninstall. If it installed in its own directory, possibly creating symlinks in
Fifth, packages often need some tailoring to fit in well with your distribution (think menu entries, file locations, etc.) With prepackaged software, this has been done for you.
All in all, a good package manager beats compiling from source any day. Debian's package management tools are very very good, and the reason I prefer Debian over any other distro. They resolve dependencies automagically (which RPM-based distro's are finally beginning to get working), and if you want, you can build the package from source with all the tweaks you want.
Re:Who needs em? (Score:4, Insightful)
- doesn't resolve dependencies
- requires dev headers installed
- takes forever
- results in cryptic error messages on failure
- has no uninstall
- is confusing for many experienced users, let alone newbies
- often requires cryptic options (--enable-foo etc)
I've used linux for years and I still consider installing from source a last resort. It may have more geek-cred, but that doesn't make it a good thing.
Re:Who needs em? (Score:2)
1. The ability to build on one machine yet install on another.
2. The ability to build on one architecture yet install on another.
3. The ability to perform you compiles in one highly observed area instead of tracking down multiple remote compilations and debugging them from afar.
4. The ability to not worry about current compiler installation and build tools on all platforms, just the one you're developing / building on.
5. The savings in time
Re:Ugh, I hope not (Score:5, Informative)
And apt-get is supported by more and more RPM based distro's, including Fedora. Dragging out apt at this point as an argument for Debian packages is a strawman - Apt haven't been tied exclusively to Debian for a long time.
Each time this discussion comes up I wait for arguments as to why Debian packages are supposedly superior, and why it matters, but so far I have yet to see any arguments presented with actual reasoning behind. I'd love to know what's so great about them... Somebody care to try to enlighten me?
Re:Ugh, I hope not (Score:2)
It's the Debian project that makes Debian great, not the software itself.
Re:Ugh, I hope not (Score:2)
I have no idea... (Score:2)
Kjella
Re:Fedora has best packages (Score:2)
With Debian, we have apt, more packages than any other distro, and a more thorough and sane policy.
Before you decry me as biased, do some research and find out for yourself.
Re:Fedora has best packages (Score:3, Informative)
With Debian, we have apt, more packages than any other distro, and a more thorough and sane policy.
With Mandrake, we have urpmi, apt, yum, policies [mandrakesoft.com], more tools to automatically assist in generating quality packages [mandrakesoft.com], more tools to check packages for adhering to policies [mandrakesoft.com], and we're rapidly catching up [mandrakesoft.com].
Plus, we have a working GUI installer
Do some reasearch and find out for yourself [mandrakesoft.com]
Mandrake had (package installation tools) first (Score:3, Informative)
Which Mandrake has had for a few years now. Both apt (and synaptic) and yum are in contrib (and have been for a while).
Anyway, Mandrake has more packages
Re:Wrong (Score:3, Informative)
And, Mandrake adopted apt quite early on [mandrakesoft.com] as well.
So, no, I don't think I am wrong, since in January 2003 we had them all in contribs (ie part of the distro).
Re:No, we still don't have cross-distro rpms (Score:3, Informative)
While we may have renamed them to have saner library handling, there are provides in the packages to keep them compatible with the broken RH names. If you find one where this is not the case, feel free to submit a bug report [mandrakesoft.com].
I won't bother with the rest of your FUD.
Re:YaST (Score:3, Insightful)
Well, then, if you have made a package, upload it to incoming, send a mail to cooker, and someone will check it and upload it.
But, in the meantime, change to the directory above the one that holds your RPMS (ie the result of 'rpm --eval %_rpmdir') and run 'genhdlist