snapmergepuppy launch

Thanks to playdayz who posted some links on the "disappearing sound" and other issues being worked on by rerwin and shinobar:
http://bkhome.org/blog/?viewDetailed=02623

Rerwin has done some in-depth analysis of some issues in Lucid Puppy, one of which is "disappearing sound" that some users have reported when running from a Flash drive. I have downloaded rerwin's "patch6" and have just started to take a look into it.

My first tentative step is to re-examine the timing of execution of 'snapmergepuppy' when a package is being installed or uninstalled...

When the Puppy Package Manager is running, the script /sbin/pup_event_frontend_d will not call snapmergepuppy, so you will never get a save of session during a package install or uninstall.

The converse is also true: if snapmergepuppy is in the midst of running when you decide to unstall a package, then the script /usr/local/petget/installpkg.sh will wait for the save to finish before installing the package.

One thing that seemed to be missing, is when you uninstall a package, there should also be a test to ensure that snapmergepuppy does not run in the midst of an uninstall operation. I have added code to /usr/local/petget/removepreview.sh to take care of this.

See commit 'c85e9aba0a' 2011-12-28:
http://bkhome.org/fossil/woof2.cgi/timeline


Posted on 28 Dec 2011, 20:01


Comments:

Posted on 29 Dec 2011, 8:11 by bigpup
Update of Woof?
Quote:
One thing that seemed to be missing, is when you uninstall a package, there should also be a test to ensure that snapmergepuppy does not run in the midst of an uninstall operation. I have added code to /usr/local/petget/removepreview.sh to take care of this.

Question?
When you make changes like this one.
Should it be offered as a general bug fix update for all latest Puppies? An update pet?
Should we all wait until the next version of Woof and someone to use it?

Idea for woof in general.
When a new version of Woof is released. How do you know the changes, from the last version, all work?
Seems a test build, of a basic Puppy, would be needed for full testing.
Seems a lot of problems, with new versions of Puppy, come back to core programs or files in Woof, that needed heavy testing.
Above topic may be good example.

I know I and probably others, would be willing to test a Woof Puppy test version prior to new release of Woof update.



Posted on 8 Jan 2012, 20:38 by BarryK
Testing Woof updates
When you make changes like this one.
Should it be offered as a general bug fix update for all latest Puppies? An update pet?
Should we all wait until the next version of Woof and someone to use it?


Not when I'm wearing my "Woof developer hat". Then I'm just developing. Puppy builds are a different matter.

Update PETs can be created by the puplet maintainers/developers, that is up to them.

As for Wary and Racy, my two puplets, there will be an update for testing sometime.



Posted on 9 Jan 2012, 4:35 by mavrothal
buidin files
Speaking of woof, I was wondering how the /root/.packages/builtin_files/ entires are generated. Looked in woof code but couldn't pin point it.
The issue is that in many puppies there are actual files not reported in any package, and packages reporting non-existing files.
Could be the developers manually modify the builds/pets of course, but is good to know anyway.
Thx.


Posted on 9 Jan 2012, 8:23 by BarryK
re builtin files
mavrothal,
That is done in '3builddistro' script, line 1901 onward.



Posted on 13 Jan 2012, 8:43 by K Godt
/usr/sbin/snapmergepuppy @PUPMODE 5
I have implemented some code to run snapmerge at pupmode 5 having clicked a savefile :

savefile="${DISTRO_FILE_PREFIX}save-";BASE='';

if [ "$PUPMODE" == '5' ];then
BASE=`mount | grep "$savefile" | cut -f 3 -d ' '`
[ ! "$BASE" ] && exit 1
fi

.
.
if [ ! "$BASE" ]; then

if [ "$SAVE_LAYER" ];then #defined in PUPSTATE
BASE="/initrd${SAVE_LAYER}"
else
BASE="/initrd/pup_ro1"
fi
fi
echo "Merging $SNAP onto $BASE..."


The code is not uptodate but i posted to give an idea of it .