[wplug] apt4rpm

[Jeremey Wise]

On Thu, 2005-01-13 at 15:55 -0500, Vanco, Don wrote:
> >-----Original Message-----
> >From: wplug-bounces+don.vanco=agilysys.com at wplug.org 
> >[mailto:wplug-bounces+don.vanco=agilysys.com at wplug.org] On 
> >Behalf Of Karlos Abel
> >Sent: Thursday, January 13, 2005 3:53 PM
> >To: General user list
> >Subject: [wplug] apt4rpm
> >
> >
> >I just got apt4rpm working on my SuSE 9.2 box.  I put a few 
> >repositories
> >in there, upgraded a few specific packages, but now have a massive list
> >of upgrades to do.  I might add that I have a lot of packages installed
> >on this machine for various reasons, none of which are particularly
> >impressive.  Here's my question(s):
> >
> >Should I give apt4rpm free rein and turn it loose, or select certain
> >packages (!) or what?  What about kernel upgrades?  Are these generally
> >wise to perform via apt-get?  I tried to RTFM but that was mostly
> >technical stuff.
> >
> >Any help would be greatly appreciated.
> 	One of my cohorts in crime here runs SuSE and uses Red Carpet to
> manage packages.  He finds that this _really_ messes up SuSE, or at
> least updating SuSE by any other means.  What is the compelling reason
> to use a package manager other than SuSE's native or Red Carpet?
> 
> Don
> 
As the above said "cohort in crime" my $.02 is that SuSE is not friendly
with other package managers. It's ability to write the secret sauce of
the configuration files that it does after adding packages get majorly
broken if you add a non-SuSE package. I no longer use Red-Carpet for
that reason even though it means I have to stay with older packages. As
an example I have been trying to get LANVideoClient working on my system
and their are lots of libraries that seem to be their but not 'their'
according to SuSE. 

> _______________________________________________
> wplug mailing list
> wplug at wplug.org
> http://www.wplug.org/mailman/listinfo/wplug
-- 
Thanks,

Jeremey Wise
jeremey.wise at agilysys.com

All opinions or information expressed here are personal in nature and do
not reflect the official position of Agilysys Inc.