On Fri, 2006-06-02 at 02:20 -0400, Bob S wrote:
On Thursday 01 June 2006 19:59, Mark A. Taff wrote:
To summarize the previous discussion about apt and suse's package management:
1. The rpm packages for KDE updates have been removed from the apt repository at ftp.gwdg.de, with more packages to be removed in the near future. 2. Apt will not work with the opensuse build service. 3. The opensuse build service is *ALPHA* software. 4. An as-yet-unreleased future version of apt4suse might work with the opensuse build service. 5. Using packages from the opensuse build service will will tie you to the bugs and features of the version of KDE initially released with the version of suse (i.e. 10.1 users will be stuck with KDE 3.5.1, even though three additional bugfix, translation and new feature releases will have been released by this August--3.5.4 gets tagged at the end of July). 6. There is no equal or superior package-management program available for SuSE that could replace apt. Yast most certainly isn't, and from my research, neither smart nor yum are as capable as apt (though they might become so if missing features are added in future releases).
So not only has the best package management system been effectively killed without a suitable replacement, but future (and current SuSE KDE packages) SuSE packages will be a far lower quality (missing recent bugfixes, translations, etc). These are two core defects that are the core of what a distribution is supposed to do: provide software.
Here here !!! Right on! Just don't know why SuSE can't take apt and adopt/adapt this superior package handler that has been proven for many years now.
Am I missing something? I thought the SUSE build server was a place to build applications. Hence the rather obvious name - oddly not called the package server. You know: unpack;configure;make. Resolving whatever dependencies are needed. Eliminating duplicated effort since dependent packages built by others are available on the same server. Leaving the compiled application for others to use as they see fit. Isn't that the case? Packaging, on the other hand, is a different, later activity. Having built your favorite package on the build server, kind souls (if not the application builder) can then package them for apt, YOU, YASY, YUM, SMART, ISOTW, whatever. And, by having the same compiled package publicly available on the build server, all these different package formats can really contain the exact same binaries. And, they can even begin to have similar dependencies. It is a real PITA when an, say, an APT packaging by one person has a dependency that conflicts with some other person's package. That is where I thought the build server came in. But I do wonder why the SUSE 10.0 repositories are gone before they are completely replaced with the new ones. Unless I am blind, I do not see all the 10.0 SUSE repositories that were on ftp.suse.com on OpenSuse. At least not in a way that a new installed 10.0 recognizes. Please correct me if I am wrong. These things are changing faster than I have time to keep checking. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com