Idea for Update Extensions

[Guy]

With version 2.4, it may be difficult for new users using wireless or dialup internet to Update Extensions. However, it can be done.

With new ideas you are trying (if I understand correctly) there may the possibility of malfunctions when updating extensions.

Here is an idea to consider.

Instead of downloading new extensions to the /tce directory, have the program create a new directory, for example it may be /tce/tmp, and download new extensions to that directory.

Have it designed so when the computer is turned off, files from tce/tmp are moved to /tce, and /tce/tmp is deleted.

That way new versions of programs would be started when the computer is rebooted.

Updates could be downloaded without special boot options.

There should be no chance of malfunctions.

It would be very easy for new users.

This is just a suggestion. You decide if you think it is a good idea.

[vinnie]

I disagree
Now just remove the pen and move the files by hand to do what you say.
If it were as you want to install directly TCE on the pen would be impossible.
I believe that the best solution would be choose the directory where to install with one options on appbrowser and leave the default comportment as it is now.
   
This would be good because for example if I unmount the flash drive the packages are not installed in /tmp/TCE but in my home! this is very inconvenient for data backup on mydata.tgz.
 The only solution for now is to use the command

Code: [Select]

approwser /tmp/TCE when needed or use tce-load point in correct directory.

[roberts]

With version 2.4, it may be difficult for new users using wireless or dialup internet to Update Extensions. However, it can be done.

With new ideas you are trying (if I understand correctly) there may the possibility of malfunctions when updating extensions.

Here is an idea to consider.

Instead of downloading new extensions to the /tce directory, have the program create a new directory, for example it may be /tce/tmp, and download new extensions to that directory.

Have it designed so when the computer is turned off, files from tce/tmp are moved to /tce, and /tce/tmp is deleted.

That way new versions of programs would be started when the computer is rebooted.

Updates could be downloaded without special boot options.

There should be no chance of malfunctions.

It would be very easy for new users.

This is just a suggestion. You decide if you think it is a good idea.

In 2.5rc2 tce-update takes into consideration wireless and/or other net access issues, by allowing updates to occur with user selectable options to minimize malfunctions.  During this rc cycle, lets try the options in 2.5rc2.

I did consider an option as suggested, but I have concerns on space requirements, up to double the size of current tce directory and on a smallish device, pendrive, or CF, etc, could be problematic.

[Guy]

Robert

I understand that you have decided not to use this idea at this time.

I hope you reconsider in the future.

Another option to consider.

Before updating extensions, have the program list all extensions which have updates available.

Enable the user to select which extensions they want to update.

People with a small amount of free space on their drive could select, one or a few extensions. The next time they use their computer, they could update others. This would overcome any concerns for those with little free space on the drive.

It would also give all users more options.

[Guy]

With all of the extensions having been updated recently, if someone was to Update Extensions it would take a long time, depending on how many they have installed.

It would be nice to have the option of just updating some, and updating others later.

[jpeters]

With all of the extensions having been updated recently, if someone was to Update Extensions it would take a long time, depending on how many they have installed.

It would be nice to have the option of just updating some, and updating others later

...okay, so there's the "update" script.  Actually, it only takes a few seconds per extension (with a fast broadband connection).

[roberts]

Guy wrote:

Before updating extensions, have the program list all extensions which have updates available.

Enable the user to select which extensions they want to update.

I belive you wrote this in response to the "command line is too scary".  As some users do not know what to do at the command line, how to exit, startx, reboot, or poweroff. Therefore another tiny fltk GUI would be more user friendly, but also require more disk space for the new extensions.

I will consider.

[JoXo009]

Hi Guy, you made the suggestion:

It would be nice to have the option of just updating some, and updating others later.

Actually I'm about developing a similar solution for a virtual install at least. See screenshot below:


Menu item 'Update', black aterm 'Update Applications' as main information window, transparent aterm displaying single repo messages and Xdialog for doing commands by mouse click - as well as menu item 'Cleanup' for deleting security snapshot, offering rollback in case an update shouldn't work properly.

Do you think, its necessary to add the option of executing part of needed updates only?

[Guy]

Do you think, its necessary to add the option of executing part of needed updates only?

I think it is a good idea.

There may be some people who want to continue using older versions of some programs, and not update them.

There may be time limitations, so they could update some now and others later.

It also addresses the ideas raised earlier on. If the idea suggested in the first post was implemented, extensions could be updated without any special boot options, and be foolproof. It also addresses the concerns about limited drive space.


I think it would be a good idea to introduce into a regular installation.

[Guy]

some users do not know what to do at the command line

There are many different people using Linux. Some have an in-depth understanding, some have some understanding, and others have quite little understanding.

The more difficult it is for those with little knowledge to use Tiny Core, the less people will use it. It may always be thought of as a specialist distro for more experienced users.

The easier it is for those with little knowledge to use it, the more people will use it. It may finish up as a serious competetor for any mainstream Linux distro.

I believe that anything which makes Tiny Core easier for new users will eventually result in more people using it.

[JoXo009]

Hi Guy,
I didn't got enough time to create an extra menu sequence for excluding files from updating - it's not trivial when it comes to dependencies.

So I just created the possibility to create and edit an exclude list, resulting in the following screen:



Do you think, that's in line with your suggestion?

[Guy]

I am not using it, so I don't know how it works.

Does it work on a conventional installation? That is what most people use.

Dependencies need to work. It would be ideal if you could list programs, not extensions, then automatically include all dependencies when updating any program.

Ideally, include the idea from the first post. Download extensions to another directory, and copy them to the tce directory when shutting down. That would make it foolproof. Even if this was just another script, which the user needed to activate.

If you don't get dependencies working, you could download the selected extensions to another directory, but not move them to the tce directory until some time in the future after they are all downloaded.

Keep up the good work. You may finish up with something worthwhile.

[roberts]

I am updating tce-update with an easy mode. Look for this starting with  v2.7rc1
Easy mode checks available space and proceeds when sufficient into an upgrade folder..
Updated extensions are moved into tce folder upon reboot. This is as user Guy had suggested.
When space is not sufficient it proceeds as before with an in-place update. Other improvements are as suggested from irc will be included.

[baz]

I'm nobody, but I love it.