Quote:
Originally Posted by tshering
Welcome to the forum,
I am glad that you like KSM. The packages are tgz-archives. That means you can simply extract the content and see what is inside. You can change things as you see fit, and re-pack them.
|
Indeed this is true. But according to me there are some problems with this approach:
- It is difficult to keep track of changes from one release to the other.
- Without using a CVS (Control Versioning System) it is very difficult to collaborate and to receive contributions to the project.
Without providing a good documentation and some easy way to collaborate usually project are going to die soon. I know that this is a big effort, and not an easy job, but I'm ready to give my contribution.
Quote:
Originally Posted by tshering
You will see that a large part of KSM consists of sh scripts. This makes it easy to change things or add new functionality. Everybody is invited to share his scripts on this thread. As for the included binaries, they have different sources. At the bottom of the first post you can find links that will lead you (eventually) to the sources of some of them (see "The package contains materials provided by ..."). And yes, some sources are not published.
|
Which are the sources that have not been published?
If I understood correctly, flashing the KSM package over an original firmware, the
/etc/init.d/rcS is the only original file that is overwritten (Am I wrong?). To make the package compilation/assembling reproducible starting from an original firmware we should provide some kind of patch file instead of the already modified complete file.
In such a way that is also easier to understand which are the addition/deletion with respect to the original file.
I really want to valorize the great work and the effort that you're putting in this project and make it easier to collaborate, giving it a chance to last longer.