| |||||||||||||
Getting multiarch dpkg into DebianGetting multiarch dpkg into DebianPosted Mar 7, 2012 20:44 UTC (Wed) by vonbrand (subscriber, #4458)In reply to: Getting multiarch dpkg into Debian by Cyberax Parent article: Getting multiarch dpkg into Debian
Haven't used --force for untold ages here... forcing the installation of something without the proper dependencies will brew trouble. Yes, the RPM format allows relocatable packages; in practice making something relocatable is a major undertaking, for very little use (so almost nobody hops through all the required hoops). Small wonder. Yes, just installing some random arch's libraries and executables and then having the whole thing magically run would be nice... if you are into that. If the software is open source, a native (and thus presumably much more performant) package is at the end of your fingertips, so this point is moot for most of the user population anyway.
(Log in to post comments)
Getting multiarch dpkg into Debian Posted Mar 7, 2012 22:53 UTC (Wed) by Cyberax (✭ supporter ✭, #52523) [Link]
>Yes, just installing some random arch's libraries and executables and then having the whole thing magically run would be nice... if you are into that. If the software is open source, a native (and thus presumably much more performant) package is at the end of your fingertips, so this point is moot for most of the user population anyway.
Nope. Quite a significant part of 'regular' Linux population uses bi-arch support every day. And it's going to get even more complex with the new x32 architecture.
And it'll mostly 'just work' in Debian.
Getting multiarch dpkg into Debian Posted Mar 8, 2012 2:27 UTC (Thu) by rahulsundaram (subscriber, #21946) [Link]
Most users who use bi-arch use it to run 32 bit binaries on a x86_64 system which has been supported in RPM for ages already and works fine. Debian has addressed a larger design and in a more generic way and has taken longer to do it. Just a different design goal and choice which is understandable. No need to bring silly things --force (which I have never used in over a decade with RPM systems and there are really zero reasons to do it) and relocatable RPM packages( haven't come across any in the real world) into the discussion.
Getting multiarch dpkg into Debian Posted Mar 9, 2012 20:19 UTC (Fri) by mlankhorst (subscriber, #52260) [Link]
Yes, the rpm packages don't need --force, unless you start actually using any -devel and then you have to use it all the time, which is annoying if you actually want to upgrade packages, since there is no yum --force..
Getting multiarch dpkg into Debian Posted Mar 9, 2012 20:49 UTC (Fri) by rahulsundaram (subscriber, #21946) [Link]
Just so that you know, I maintain over 100 RPM packages and never had to use --force even though I routinely use -devel packages.
Getting multiarch dpkg into Debian Posted Mar 12, 2012 13:24 UTC (Mon) by mpr22 (subscriber, #60784) [Link] It seems to me that if a -devel package has to be --force'd, you should examine why - then either fix the cause if it's at your end, or file a bug report if the cause is at the package maintainer's end.
Getting multiarch dpkg into Debian Posted Mar 13, 2012 12:00 UTC (Tue) by mlankhorst (subscriber, #52260) [Link]
oh but then I look it up and it's already been a bug for the past 3 releases of fedora with nothing that has been done to fix it. llvm devel packages have the same issue, also not fixed.
|
|||||||||||||