Among the highlights for AbiWord 2.8 include annotation / comment support, support for smart quotes, multi-page document viewing, true SVG (Scalable Vector Graphics) support, improved support for OpenDocument Format and Office Open XML file formats, a new printing framework, and much more.

Please consider updating the remaster script to provide an option to select a directory or a CD for the files to copy. The present script results in a lot of extra coasters. I prefer to create an iso and check it out thoroughly before burning it to CD.

This feature is in Dougal's upgrade of Barry's original pupremaster. Dougal's pupremaster.sh still works fine from a directory, however there must be a zdrv_xxx.sfs in the directory and many derivatives don't need one. Also, the resulting iso has to have some minor edits for it to work with the latest derivatives because of some syntax changes.

Isn't this the one that does away with the xorg configuration file? If so, I want to be sure we all know how to do manual reconfiguration before we jump in with that - Probably break a few wizard scripts as well because of this.

Of these three, I prefer Dougals, however due to naming changes in later distributions, the resulting iso has to be edited before it can be used. Also you must have a zdrv_XXX.sfs even when it's not needed, otherwise your directory will not be recognized.

The other two don't allow using a directory from which to copy the files which can result in burning a lot of unnecessary CDs.

Not unless, pa_mcclamrock changed his mind, because I specifically addressed this with him during development and he would not include that feature, just suggested that I use R/W CDs. After my request was refused, I never looked at it again.

Being able to remaster without a CD would be a HUGE plus. I rarely actually burn copies of the ISO's i download. I usually just rip them apart and make save files for them. Being able to remaster without CD's would be a great feature. Just my 2 cents.

I am preparing to upload this to the Google Code Repo, but wanted to first apologize to pizzasgood that it still has Barry's pinstall.sh scripts from 2.9 because I am not sure how to fix it for multiuser without breaking it for the woof build system. Then again I am not set on using woof if Pizzasgood's build system will work better for Puppy only stuff (no debian, slack, arch....)_________________Web Programming - Pet Packaging 100 & 101

Actually, that should work fine with how I did things. Instead of figuring out how to make packages that install to /root be friendly to multiuser, I just set up the createpuppy script so that after all the packages have been installed and the pinstall.sh scripts have been run, it copies /root to /etc/skel and then does some processing on it.

That doesn't help when the user installs a package that wants to modify /root. But on the other hand, packages likely to be installed by the users probably shouldn't be touching /root (or ~/) in the first place. (It's tolerable for some of the core stuff that Puppy comes with, since we want to ensure the user has a nice desktop already set up. Though maybe it would be better to separate that part from the actual package or something. Not sure. Haven't thought much about that. A lot of this stuff starts getting subjective.)

If at some point root wants to update /etc to match /root, he can use the populate_skel script I wrote.

I have not used Woof yet (beyond dabbling one weekend last spring) so I can't make any real comments on whether we should use it or not. But I figure it's probably a better option than Unleashed, if for no other reason than because it's more up to date and is being actively maintained by Barry himself. It also sounds like a more flexible system._________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

I made a pet of dia diagram editor and compiled with NLS support but stripped the locales and rebuilt all of the large localized files using sed. After stripping the mostly redundant CISCO shapes it is down to about 1MB. I can make those stripped parts available too if anyone is interested.

P.s. I named it diat (for dia tiny) Feel free to strip it down further by removing the /usr/share/dia/sheets and corresponding /usr/share/dia/shapes_________________Web Programming - Pet Packaging 100 & 101

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum