Mailinglist Archive: yast-devel (116 mails)

< Previous Next >
Re: [yast-devel] introduce a package history to remove obsoletepackages
  • From: "Dominique Leuenberger" <Dominique.Leuenberger@xxxxxxxxxxxxx>
  • Date: Wed, 11 Jun 2008 08:14:08 +0200
  • Message-id: <484F975F.2554.0029.1@xxxxxxxxxxxxx>
On 10.06.2008 at 18:04, Ricardo Cruz <rpmcruz@xxxxxxxxxxxxxxxxxxx> wrote:

I like the idea, though you're making it more complicated than it
needs, but those dependencies are only dead disk space. If they conflict
with something, they'll be removed or upgraded then.

I think there are more important flaws with Suse's package system.
There is no layers in there which would make stuff like what you're
talking about simpler, and could allow for some interesting uses. Of
course, there is a certain terminology that packagers tend to respect.
But most fundamentally, it would be cool if the packages database was
the directory structure itself. This is when the clutter gets in: a lot
of people don't want to be bothered about doing a RPM package, and you
get a mess, because stuff gets installed all over /user, and this can
actually result in conflict if you don't clean it up.

Well, the different points on the disk, where files have to go to, are
perfectly defined in FHS. Do you suggest something like at good ol' dos where
one program was in one folder? And all the data of that program was there too?

I doubt that I would like to live with such a installation on my system: just
imagine having such a system with remote file systems and then maintain it.


To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups