This (click on the blue word) is of grave concern to me, and I think that
it should be for all Puppyists as well.
Which is why I am opening this thread in the "Announcements" section.
The title of that "commit" at woof CE is:
"init: refuse to load pupsave if WOOF_VERSION differs"
This means that any old pupsave you may want to incorporate to a new
Pup will be rejected. This, in my mind, is a Stalinian move. It will also
prevent devs from using a pupsave created with dd etc, to be used as an
assistant in the development of a Puppy -- like I am doing now.
This is very close to a personal attack, to me, but also to Puppyists'
freedom of using their Puppy as they see fit.
I totally agree with peebee's comment at bottom of that page:
Puppyists should don their "yellow jacket", go out in the streets and blockpeabee commented on 4c4e139 22 hours ago
I am unsure whether this change is in the spirit of Puppy - refusing to load
a pupsave is very draconian.............advice on how to change things if
people do want to take the risk should be provided.........
highways and roads over this. This is the most serious and dangerous
limitation I have ever seen brought to Puppy in the 10 years I have been
a member of this forum.
In my mind, this makes wdlkmpx, the author of that commit, "Enemy #1"
in Puppyland, the foe to be taken down no matter what.
I am for structure and order in development. However, I am and will
forever be against arbitrary, "committee-driven", development.
If you want to turn people away from Puppy, imposing that limitation on
pupsaves is the way to go. If this goes through, this is the beginning of
the end of freedom in PuppyLand. Mark my words.
Shame on you, "wdlkmpx", for even thinking of such a base and limiting
idea, whoever you may be on this forum.
On the contrary, pupsaves should be made as "universal" as possible,
so they can be portable to any Puppy.
BFN.