scms locales are not automatically loaded

[AbNoRMiS]

when i tested these changes i found some "features" at work with scm
1. if been downloaded and installed tcz extension then scm deps
    with a similar names can't be downloaded and installed (for example gtk2)
2. scm are repeatedly added to scmboot.lst without their checking in this list
3. when deleting scm ( scmapps -> apps -> local -> delete -> go )
    then its name are not deleted from scmboot.lst
4. and now the most interesting
    when deleting an scm then will be deleted tcz extension with a similar name
    for example tar.scm, tar-locale.scm etc (and yet i had installed abiword.tcz )

[AbNoRMiS]

Removed attachment as it is against forum policy.

dear roberts
sorry, but i do not quite understand what exactly i violated from below mentioned
http://forum.tinycorelinux.net/index.php/topic,7738.0.html
http://forum.tinycorelinux.net/index.php/topic,5287.0.html
i proposed changes to the existing system script and expressed this on the forum
i marked amended and attached a modified script for testing
because i have not found anything other than ban attach binary extensions
attached script does not violate the integrity of the system or its operation
may i something incorrectly translated and not exactly understood?
please forgive me if i'm wrong but please explain this to me

[roberts]

The same respect affored to extension makers applies to base system fucntions.
You do not decide to take control of  someone's  extension. We do not want multiple varations of core system functions. Especailly when a discussion was ongooing. There are exising ways to solve wihtout hard coding.

Please show respect and do not post replacements for core functions.
Ideas, suggestions, and discussions are welcomed. Posted replacements of core functions especially as attachments are not. User posted replacments would become a support nightmare.
Please let myself and the team handle the core there are plenty of new requested extensions that you can contribute.

[roberts]

Back to the topic:

Many ways to handle. Some are quite easy. Note that not everyone needs a locale file.
In order of ease and least impact:

1. Add needed locale.scms to scmboot.lst  (Easy)
2. Manually load locale when loading the base scm via ScmApps GUI. (Simple)
3. Create a .dep file for the locale.scm indicating the base scm name. (Less simple)
4. Embed every local.scm into the base scm extension. (Much larger downloads)
5. Hard code searching for a corresponding locale file for each and every extension install,  uninstall, and deletion. ( Impacts every user and every action for every extension).

[AbNoRMiS]

The same respect affored to extension makers applies to base system fucntions.
You do not decide to take control of  someone's  extension. We do not want multiple varations of core system functions. Especailly when a discussion was ongooing. There are exising ways to solve wihtout hard coding.

Please show respect and do not post replacements for core functions.
Ideas, suggestions, and discussions are welcomed. Posted replacements of core functions especially as attachments are not. User posted replacments would become a support nightmare.
Please let myself and the team handle the core there are plenty of new requested extensions that you can contribute.

with great respect roberts thanks for your explanation
in any case I did not mean disrespect of your work and team
i just tried little help in improving your unique like me think system

[AbNoRMiS]

if there be accurate then going back to the topic title involves automatic loading locales
unfortunately none of the proposed first four decisions can't considered fully automated
but if already decided not to resort to hard coding then will have to use available means
thanks

[Jason W]

Perhaps since scm extensions are usually downloaded once and put on hard storage, and their updates are small with the use of zsync, maybe it would be simplest and best to just include the locale files in the scm, keeping with the self contained concept as much as possible. 

On looking at the locale situation, my vote is for simplicity of included files.

[Jason W]

The team has discussed the scm locale situation and has opted for the simplicity of including the locale data in the scm.  I will pack the files in the existing scm's, and any new ones will simply include them.  Even the largest apps will rarely take over 5mb of compressed locale files, so the cost should not be significant.

[AbNoRMiS]

do not you think that is very controversial decision was made?
if follow the tinycore principles of minimalism
then need separate the locale from main modules
because how to deal with such cases as these

gimp2-basic-locale.scm - 12.5MB
gimp2-basic.scm - 8.5MB
gtk2-locale.scm - 10.8M
gtk2.scm - 11.4M
gtk3-locale.scm - 10.5M
gtk3.scm - 9M
pidgin-minimal-locale.scm - 8.5M
pidgin-minimal.scm - 10.2M

it seems that such cases may be more than desired
when locales are the same or even larger than main modules
and purely english-speaking users are also not few

[Jason W]

My initial motive for separating locale data was that they tend to be large, and are used by the minority.  They are very easy for those who want them to load them and include them in scmboot.lst.  Those who do not need them will never download or install them.  For those who use them, once in scmboot.lst they are always loaded and available.

Locale extensions are very easy to find, easy to load, and easy to unload for those who need them.  But as it apparently is not satisfactory to require loading -locale extensions and automation and thus complexity was desired, we opted for simplicity.

[Rich]

Hi AbNoRMiS
While one of the core principles behind Tinycore is a small footprint, the point behind an scm is to be self contained.
As a result, scms are larger anyway since they contain private copies of libraries that would normally be shared
between extensions. Personally I think it makes sense from a self contained point of view to include locales.

[AbNoRMiS]

murphy was right: any solutions breeds a new problems
frankly if my wish then i would leave as is now, it would be the easiest solution
but i think after some time someone will offer question of locale automation again
i am sure in this because even before this topic was established
i would propose changes to automatic download, install and remove tcz locales
 

[Jason W]

It really is a shame that now someone is going to have to download and store a 20MB extension instead of an 8MB one in the case of gimp2-basic.scm.  Or 22MB instead of 11MB in the case of gtk2.scm.   All because one or two people were not satisfied with having to go through the effort of clicking "Install" in the Scmbrowser to install their needed locale extension data.

[AbNoRMiS]

must confess that i been one of those three people
but then the other two diverged for some reason
 

[Jason W]

I spoke in a moment of frustration, it is not really that simple nor for that reason that we are going to include locales in the main scm extensions.  Though sure, this thread sparked that debate, there were several issues to consider regarding loading, unloading, etc. .

Mostly, we don't want the scm to head down the slippery slope of feeling it needs to compete with the tcz in terms of modularity, size, etc, therefore diluting it's main goal of being self contained.  Larger downloads are just part of that concept.