- a good package manage system
Actually we started working on this this week :-)
ok.
- an integrated product
In which ways do you lack integration?
well basically it boils down to that im a kde user, and slowly i got more and more gtk based apps running by default. i dont mind gtk, for gimp or inkscape, or whatever. but i do mind beagles and updaters and ZEN-stuff that comes in, falling from the sky, hurting my system performance, not integrated with my desktop. i dont need mono running. i dont need 2 toolkits loaded. i just want an integrated desktop 'experience'.
- some sane defaults everywhere
Can you please provide some examples?
like have the apps i just talked about running by default. they made my system useless. this is quite bad: i upgrade -- system gets too slow to use. of course i can turn that off... as i did. i dont know what caused it (i just moved on from suse that week), but installing a simple packages from yast took like 15 minutes (okay i like to have a lot of package repositories). 15 minutes to install a 15k package! i can do it faster by compiling it from source.
suse from 10 onward was (imho) lacking all. yast basically didn't change; it also was not very 'community'.
I see your point.
now there is the *ubuntu family that kind of save all of us by being the cool debian, and all of a sudden yast is not longer a 'strategic advantage' but a large disadvantage.
In what ways?
i way that yast was suse's property, its asset like a webserver/database/kernel/webbrowser user to be a nice product to 'have' as a company. now we have apache/mysql/linux/mozilla (just examples) so selling your webserver/database/kernel/webbrowser gets much harder. same for yast i think. there are quite solid open source 'community' replacements for yast, so it becomes a burden to maintain it inhouse as it has little added value -- so it gets open sourced.
so yast is a problem
I wouldn't go that far :-)
i understand your point. but maybe i can say 'burden' then. a burden to suse.
please think big!
We will! :-)
good.
p.p.s: did i mention that it might also be a good moment to drop RPM in favor of DEB? (this might even create a strong cooperations between suse and the debian/ubuntu/etc.)
What would be the advantage of it? Why are we using RPM instead of DEB?
it seems so much faster, and more clever... maybe my perception is a little distorted. with kubuntu i'm now installing a 15k package in less than 15 seconds; in yast it was 15 minutes -- and i still like to have many package repositories. thanks! _c. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org