On Tuesday 29 November 2005 09:42, Les Mikesell wrote:
Part of this could be fixed if the third party repositories would make the effort to split items that do/don't replace core components.
Perhaps.
However, if the repository requires those core components, does it matter whether it is in a split-out subrepository or in their main repository? If it is required it is required.
I know a little about this situation, using DAG and KDE-Redhat (my knowledge is far from exhaustive on the subject, but have had my share of 'situations'). KDE-Redhat by nature replaces large swathes of core libraries for the support of the later KDE (which is needed here for the upgraded kstars package, which we use for telescope control). DAG is a mixed bag, but not as intrusive as I found ATrpms to be. The biggest problem with DAG is the experimental apache httpd behind apt.sw.be, DAG's main mirror. I have had issues before with conflicts; when using third-party repos this just about must be expected, unless it is tailored for the core like Karanbir's extras.
One might ask why I run CentOS for stability but KDE-Redhat for a cutting edge feature together; it's called business sense, and using what is best for my needs. I don't want to go through major issues every six months like with Fedora, but I do really need the 3.4 version of kstars for telescope control. Thus far, CentOS4 plus KDE-Redhat has met my needs without being to terribly difficult (the need to download nearly a gigabyte of updates each quarter is disturbing; if Microsoft did this every quarter there would be significant outrage! I believe the scalability of delivering complete RPM updates is poor, and some rpmdelta mechanism needs to be implemented, both for the sake of the mirror's bandwidth and for the user's bandwidth). At least I'm not downloading a set of four CD's with major version upgrades of core components each six months....