Managing Software

[sefk]

IDEA: As part of the metadata provided to zypper, there could be a 'libs' file/section that contained packages to be hidden, zypper would then simply not display them in searches (this way, packman could keep libxine1 as a visible package, and users can simply install it)

Imo, there is a cleaner way to do it:

Add to yast, or create a new application, that integrate YMP's technologies. I prefer it to be a separate from yast's control center:
1: because it wont interfere with user who prefer yast's interface.
2: because it clearly shows that yast is for advanced user and the new piece of application is for newbies.
3: because yast doesn't need to be more heavy.

Little mockup:

I forget to add a refresh button.


The installer is in two sections:
Install section:
By default, the installer will fetch a list from the OSS repo containing many *.ymp (ex: the gimp, openoffice). If a user wants no-free apps, then he can click the checkbox. The installer will fetch a new list will no-free ymps availaible (java, nvidia). Same for community packages (which will add packman repo).

The advantage of ymp is that they alreay exists and they will add repos automatically, so newbie don't need to care about it. So if the user checks the no-oss box, nvidia's driver will be available to install. And if the user has chosen to install it, nividia's repo will be added.

However, if the user adds a specific repo (ex: cyberorg's), then cyberorg can add a similar list to his repo and if the user refreshes the installer, it will download it. This way, the installer is not only a good beginners' tool, but also a big ymp browser/manager.

Uninstaller:
Uninstall is a little bit more tricky, but it can be done. The uninstaller has a default lists of software that can be uninstalled and at each refresh, it will check if they have been uninstalled with other means (ex: via zypper). Also, each time the user add something with the installer, the application will log it and add it to the "uninstall lists".

The problem, is that is the user mix package manager (yast, zypper, my installer), uninstaller will have trouble to monitor everything. Of course, it's just a mock-up, so it's not perfect.

[some-guy]

Originally Posted by sefk

The problem, is that is the user mix package manager (yast, zypper, my installer), uninstaller will have trouble to monitor everything. Of course, it's just a mock-up, so it's not perfect.

It shouldn't, because it is essentially using the same thing (libzypp), this would simply be another frontend, which technically, doesn't make it another manager

[sefk]

The problem is my mock-up uninstaller works with a log system which monitor the installer. Ex: if a ymp say to install compiz and emerald, then compiz and emerald would appear in the uninstaller, but not dependencies.

The good part is since only packages available in the installer will be logged, so the uninstaller wont be flooded with files that a "newbie" doesn't want to see.

The bad part is that installations via yast and zypper wont create this kind of log (and shouldn't, since if linux's kernel is updated with yast, it shouldn't appear in my newbie installer). On the other hand, those who rely on this app to uninstall shouldn't want to use yast.

[some-guy]

Originally Posted by sefk

The problem is my mock-up uninstaller works with a log system which monitor the installer. Ex: if a ymp say to install compiz and emerald, then compiz and emerald would appear in the uninstaller, but not dependencies.

The good part is since only packages available in the installer will be logged, so the uninstaller wont be flooded with files that a "newbie" doesn't want to see.

The bad part is that installations via yast and zypper wont create this kind of log (and shouldn't, since if linux's kernel is updated with yast, it shouldn't appear in my newbie installer). On the other hand, those who rely on this app to uninstall shouldn't want to use yast.

Actually, afaik, ymp's store the packages to be installed, so it should be able to generate a database on installed ymps, and simply delete the packages and dependencies from that ymp

[john_tomas]

I liked sefk's idea...


I actually, heard that Justin was suppose to be working in something like that... Something like CNR... a 1-click install client, but I've heard that a long time ago... I think the project was never started... and i don't know if it will ever be...


but the idea of creating such software and introduce it in the regular OpenSUSE (not an newbie specific version) version would be great... this way newbies could also use it easily... not just experts... because this way newbies could explore it and someday became experts...


So, sefk's idea is actually very cool

[some-guy]

Originally Posted by john_tomas

I liked sefk's idea...


I actually, heard that Justin was suppose to be working in something like that... Something like CNR... a 1-click install client, but I've heard that a long time ago... I think the project was never started... and i don't know if it will ever be...


but the idea of creating such software and introduce it in the regular OpenSUSE (not an newbie specific version) version would be great... this way newbies could also use it easily... not just experts... because this way newbies could explore it and someday became experts...


So, sefk's idea is actually very cool

1-click installs(YMP) have existed since just before 10.3...

[john_tomas]

1-click installs(YMP) have existed since just before 10.3...

yes, I know that...
but there was never a specific client side to allow users to easily remove software installed via 1-click install...

and that's the subject here, not 1-click install

[john_tomas]

Just to update this post

there as been created an Bug Entry (request for enhancement) on Bugzilla where you can vote...

[https://bugzilla.novell.com/show_bug.cgi?id=425890 Bug 425890]