Multiple package installation/removal with PPM

Message

mavrothal · #16 Post by **mavrothal** » Mon 08 Dec 2014, 18:27

Uploaded v5
v5 reports the overall space needed before the installation begins and can be cancelled at this point.
I have the feeling that is a bit pessimistic. ie reports that more space is required than it is actually used. Please test, particularly with "big" packages with many dependencies.

The other feature of v5 is that menu and gtk-icon update as well as checking for all user-installed packages happens at the end of the process and not after every installed package as in v1-4.

As far as I'm concern all the features are there. Now we need to find the bags and hopefully the solutions. Please test.

On related issue, I found during tests that not all of the 50-some files (

) that PPM generates in /tmp are properly updated in every run resulting in strange results some times. So it is recommended that if you find some strange behavior, close PPM, run the attached clean_ppm_tmp.sh script and try again to see if the "problem" goes away.

zigbert · #17 Post by **zigbert** » Mon 08 Dec 2014, 20:53

I'm working on converting ppm to use vector-icons.
... We need more icons

mavrothal · #18 Post by **mavrothal** » Tue 09 Dec 2014, 09:54

mavrothal wrote:Uploaded v5
v5 reports the overall space needed before the installation begins and can be cancelled at this point.
I have the feeling that is a bit pessimistic.

Indeed it was.
Till the next version of the "ppm_multi" pet, the attached ppm_multi_5-sizefix.pet fixes that and now total space needed for all to-be-installed packages and their dependencies, is reported more accurately.
Please install this pet after you have installed the ppm_multi-5.pet

Edit: v6 is out and includes the changes added by the pet. The pet is removed to avoid confusion or addition to future releases.

mavrothal · #19 Post by **mavrothal** » Tue 09 Dec 2014, 10:53

zigbert wrote:I'm working on converting ppm to use vector-icons.

Isn't this going to make it more difficult to port in older puppy versions?

I said I'm not going to support older puppies but at this point I think that the current pet should work OK in some of them and easily modified by the respective "puppyteer" (

) to work with others (tested in slacko 5.7 OK. Precise 5.7.2 has issues)

zigbert · #20 Post by **zigbert** » Tue 09 Dec 2014, 14:50

mavrothal wrote:Isn't this going to make it more difficult to port in older puppy versions?

I can make it work for both mini-icons and the woof-vectors. - simple.

mavrothal · #21 Post by **mavrothal** » Tue 09 Dec 2014, 16:56

zigbert wrote:
mavrothal wrote:Isn't this going to make it more difficult to port in older puppy versions?
I can make it work for both mini-icons and the woof-vectors. - simple.

It's all yours then

Actually besides the main window, I think that all the GUI elements need some revisiting as they look like the patchwork that they are! A mix of gtkdialog v2, 3 and 4, gtkdialog-splash, pupdialog, xmessage and what not.
Even independent of the multiple package install/remove changes, the PPM GUI elements need a second look.

zigbert · #22 Post by **zigbert** » Tue 09 Dec 2014, 17:39

mavrothal wrote:
zigbert wrote:
mavrothal wrote:Isn't this going to make it more difficult to port in older puppy versions?
I can make it work for both mini-icons and the woof-vectors. - simple.
It's all yours then

Actually besides the main window, I think that all the GUI elements need some revisiting as they look like the patchwork that they are! A mix of gtkdialog v2, 3 and 4, gtkdialog-splash, pupdialog, xmessage and what not.
Even independent of the multiple package install/remove changes, the PPM GUI elements need a second look.

Let's take it step by step. I fix what I see during my digging, but I am not happy with 'fixing' stuff I can't test. In my Woof-gui-tour, I saw many boxes, I could have converted to libstardust, but I didn't, simply because I could not test the result... Another issue is that using libstardust (my choice) when staying compatible with older Puppies.

Maybe offer your version outside Woof, and include my extended gui into Woof ?

Sigmund

Sigmund

mavrothal · #23 Post by **mavrothal** » Tue 09 Dec 2014, 18:06

zigbert wrote: Another issue is that using libstardust (my choice) when staying compatible with older Puppies.

Maybe offer your version outside Woof, and include my extended gui into Woof ?

Sigmund

On a second thought I think we better look forward.
If anything libsturdust, could be offered as a dependency pet for older puppies. Although, I think that users of older puppies are usually happy with what they have and do not bother to change it.

Regarding woof, I think you may want to keep GUI changes regarding multiple package handling and traditional PPM elements separately, or at least in different patch-sets.
I would not feel comfortable to put the multiple package handling changes in woof without extensive testing, and this may take some time with the current rate...

mavrothal · #24 Post by **mavrothal** » Wed 10 Dec 2014, 11:59

Version 6 of the "ppm_multi" pet and patches is out

This version provides the option to remove individual packages from the install/remove windows without restarting the whole process.
It also provides a more accurate calculation of the space needed for installation (though I think still a bit pessimistic...).

I can not think of anything else to add/remove.
The only thing I would like to add is the refresh of the installed packages window (INSTALLED_DIALOG) at the end of the removal process, but I have no idea how to do it. I can not even auto close it since it does not appear as a different process but rather as part of the MAIN_DIALOG process

Any ideas (Zig?...)

BTW here is the new PPM in action installing and uninstalling 3 packages and their dependencies

zigbert · #25 Post by **zigbert** » Wed 10 Dec 2014, 16:58

mavrothal wrote:Any ideas (Zig?...)

I'll fix that... but let's see what interface we end up with before dealing with such minor issues

What I miss is a constant message showing up during ALL installing processes. It pops up splashes and terminals here and there, and when installing (many) big packages it's hard to know when the process is actual done.

You announced version 5 as the last one - until version 6. I am curios of v7

I'll wait a bit longer before I adds my code to your code. I have still a bunch of icons to work with...

Sigmund

mavrothal · #26 Post by **mavrothal** » Wed 10 Dec 2014, 17:29

zigbert wrote:What I miss is a constant message showing up during ALL installing processes. It pops up splashes and terminals here and there, and when installing (many) big packages it's hard to know when the process is actual done.

Yes this would be nice. The problem I see is that we have no way to estimate the overall time/processes needed and thus provide a progress bar or something. In the remove process (which is much more quite) I have every package "announced" when removed but this is not what we really need. If you have any idea...

zigbert wrote:You announced version 5 as the last one - until version 6. I am curios of v7 I'll wait a bit longer before I adds my code to your code. I have still a bunch of icons to work with...

I said is final feature wise and indeed it is. I just added the 'remove from the list' function because I would like to have something "complete" for older puppies too.
I really do not intend to add any other feature (I can not think of anything

). However I believe that some changes in the non-GUI code may occur. For example the report window shows the success/failure or the original packages but not any dependencies. Adding code to add them in the report window should not affect the GUI code. Would it?

zigbert · #27 Post by **zigbert** » Wed 10 Dec 2014, 20:13

mavrothal wrote:Adding code to add them in the report window should not affect the GUI code. Would it?

If I shall port boxes to libstardust, I guess it will affect the same files.

Sigmund

mavrothal · #28 Post by **mavrothal** » Wed 10 Dec 2014, 21:58

zigbert wrote:
mavrothal wrote:Adding code to add them in the report window should not affect the GUI code. Would it?
If I shall port boxes to libstardust, I guess it will affect the same files.

I probably miss something, but if a box presents to the user the content of a file, say /tmp/pkgs_to_install_done, and we change the content of this file to also contain installed dependencies, why this would affect the transition from a "classic" gtkdialog box to libstardust?

Anyway, a v7 can not be excluded specially if some testing by other people too, is actually done...

mavrothal · #29 Post by **mavrothal** » Thu 11 Dec 2014, 12:25

zigbert wrote:What I miss is a constant message showing up during ALL installing processes. It pops up splashes and terminals here and there, and when installing (many) big packages it's hard to know when the process is actual done.

I do not know if this will make your life any easier

but the attach pet has all information splashes and terminals removed when in "auto" mode (errors are still reported) and logs to /tmp/PPM_LOGs/ instead.

gcmartin · #30 Post by **gcmartin** » Thu 11 Dec 2014, 23:07

@Mavrothal, I rather like this contribution.

It offer great utility and I can see how this would be useful across several distros. For example, it I maintained a list of PETs for a given PUP that are individual to one's needs, I could used this list to install PETs on any distro going forward as it would maintain consistent packaging automatically resolving dependency issues as one goes.

Thanks.

mavrothal · #31 Post by **mavrothal** » Fri 12 Dec 2014, 12:33

Version 7 is uploaded
This is a bugfix update, with no new functions or GUI elements.
See first post for details.
v7 is tested (and fixed) to work in full installs too.

Zig, notice that this is not the "quite" version posted in the previous page.
If you think you can get a progress window/bar going we may want to adopt the quite version before we diverse too much from v6.
Alternatively if a progress bar/window is unlikely we can run everything in a small terminal window (with small fonts etc) similar to what the "details" window of the Synaptics package-manager/GUI does, to basically show to the user that things are going on.

zigbert · #32 Post by **zigbert** » Fri 12 Dec 2014, 13:53

mavrothal
It's a bit hectic around here atm, but next weekend I get Christmas holiday, so if I could be 'in charge' and implement gui-stuff from next weekend, it would be great. You get it back as fast as I am ready. I fear there is plenty of stuff to improve, so it may take some days.

When it comes to a progressbar, I have not looked into it enough to tell the answer. What I would like to include is a statusbar with info of your space-calculation and probably some progress info...

Sigmund

mavrothal · #33 Post by **mavrothal** » Fri 12 Dec 2014, 14:14

zigbert wrote:I could be 'in charge' and implement gui-stuff from next weekend, it would be great.

OK. Hopefully some people will actually test it and report some bugs to hopefully solve by then.

In the mean time I may go ahead and implement the "quite" mode with a small rolling terminal window to indicate progress (pic)

stemsee · #34 Post by **stemsee** » Fri 12 Dec 2014, 18:34

I will be testing it thoroughly.

mavrothal · #35 Post by **mavrothal** » Fri 12 Dec 2014, 22:29

stemsee wrote:I will be testing it thoroughly.

You better try v8 then

Is "silent", fixes a bug I found (hopefully you find more) and removed the Xdialog with the install options. This in now moved to the install/removed list window.
With the previous implementation if you had just one package to install you needed 5 clicks and 3 windows

. As many as in the classic method.
Now you need only 2 as I also eliminate the confirmation after the space-needed check. Just installs silently if sufficient or aborts and warns if not.

Note:The 1st download of v8 is a bit different then the current v8. Please re-download if you were the first to get v8

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Multiple package installation/removal with PPM