The Problems of the "Bleeding Edge"
Posted: 14 Nov 2017, 23:32
@all
It is very exciting to hear the term "Bleeding Edge",as it supposes advanced knowledge of the matter; I am one of those interested in the "last Wow" in computing... But there is a price you must pay for that: Pa...tie...ce! I will explain...
Every time you update a module, you have to run all applications you have installed, to see if they still run.
Normally it brings with it a chain reaction of module updates...at times you will think "Oh God, why did I changed that!
Sometimes you will not find a necessary update to make a favorite application to run again. Then you have to invent a little bit: normally it is a new library that is more advanced than the one asked for the program. The first thought is to add a symbolic link to the new library using the old name. Ok, but sometimes that will not work, either
Don't panic!, you can open the old module and look for the asked library, and with that you make an extra module with a different name. Just test which library/ies you need in the live side of Porteus and then make the package; this you put together with the lagging development module -at best in an extra folder- and you are done.
It is worthwhile, try it
Regards!
It is very exciting to hear the term "Bleeding Edge",as it supposes advanced knowledge of the matter; I am one of those interested in the "last Wow" in computing... But there is a price you must pay for that: Pa...tie...ce! I will explain...
Every time you update a module, you have to run all applications you have installed, to see if they still run.
Normally it brings with it a chain reaction of module updates...at times you will think "Oh God, why did I changed that!
Sometimes you will not find a necessary update to make a favorite application to run again. Then you have to invent a little bit: normally it is a new library that is more advanced than the one asked for the program. The first thought is to add a symbolic link to the new library using the old name. Ok, but sometimes that will not work, either
Don't panic!, you can open the old module and look for the asked library, and with that you make an extra module with a different name. Just test which library/ies you need in the live side of Porteus and then make the package; this you put together with the lagging development module -at best in an extra folder- and you are done.
It is worthwhile, try it
Regards!