the best way I can think to be able to remove files is to do something like
for $onedir in `ls -1 $PACKAGESDIR` do
ls -1 $onedir >${onedir}.files
done
this would establish a list of files in each pet

then to remove the files
for $onefile in $filelist do
rm -f $onefile
done

just need a frontend that downloads the <package>.files and allows you to select them for removal (currently installed packages are listed in /root/.packages/woof-installed-packages so it could technically only download the .files for programs you want to remove)_________________Web Programming - Pet Packaging 100 & 101

Being primarily an english speaker I cannot test it well, but I am at least compiling all new compiles with NLS enabled and providing a separate NLS sfs (also a DOC sfs) ... the NLS could then be cutdown on a per language basis fairly easily - no point in separating them until the final or at least the RC though. Any locale patches for exist programs are more than welcome - I will leave the vetting up to the native language speakers._________________Web Programming - Pet Packaging 100 & 101

maybe we should have a bug on the issue tracker for programs that still do not support NLS - I recompiled most of the larger, most popular programs to support it but I can only keep track of so many things. Where is droope anyways? - Wasn't he was the king of locales in 4.2?_________________Web Programming - Pet Packaging 100 & 101

What a big honor, to be called a king and by the person in charge, wow, thanks.

Firstly, i'd like to thank you for your effort towards the CE. And secondly, without intending to force you to do anything, and knowing this would be very time consuming for you, i would like to post a list of all software already localized by the community.

This is the latest of the latest, extracted directly from here and updated 28/02/10.

Also, i'd like to add a list of things that could be of interest in order to provide localization. From here, an extract:

Quote:

One thing I believe still needs attention: that ordinary, unlocalised Puppy be able to display non-Latin characters in dialogue boxes and window title bars. (Assuming, of course, that the necessary fonts have been installed.)

any of localisation on X failes because of the bug in /usr/bin/xwin.
see http://www.murga-linux.com/puppy/viewtopic.php?p=325229#325229

Quote:

maybe we should have a bug on the issue tracker for programs that still do not support NLS - I recompiled most of the larger, most popular programs to support it but I can only keep track of so many things. Where is droope anyways? - Wasn't he was the king of locales in 4.2?

I'm still arround The issue is I do not have as much free time as I did last summer, and have no computer installed at home.

But I will continue to provide support where I am able to, do not hesitate to PM! Always available and willing to help. Will make an effort to give some love back to the comunity

Cheers!
Droope_________________What seems hard is actually easy, while what looks like impossible is in fact hard.

“Hard things take time to do. Impossible things take a little longer.” –Percy Cerutty

4.4 Pre Alpha test run has its own thread and then we have this thread.
Is this the one I should report feedback on behavior in?

Well I downloaded the latest iso again and did a fresh pfix=ram frugal install using Technosaurus own menu.lst and it still fail to do Swedish or Finnish keyboard from Sweden or Finland. Have not tested to do Denmark or Norway.
Now I need to do setxkbmap se to get my keyboard right.
pups save doesn't save the changes of what keyboard one want to use.

Icon on Desktop for Drive, My links and files are missing after reboot.

When are you planning to update the iso with all the fixes?

Can I tell the os to use setxkbmap se in the menu.lst or should I somehow open some xorg config file somewhere and changes us to se ?

side note

what is that T2 that James talks about and where is the iso for that one?

James C wrote:

@ Nooby,

TPup is based on T2 and uses it's repository.....not Tiny Core.

As far as I know there is way to convert Tiny Core packages for Puppy use though.Believe there was a thread over in the additional software section of the forum.

I trust that if Technosaurus name it TinyCore respositories then it is TC but he has changed them to also be sfs ones on the asia site?_________________I use Google Search on Puppy Forum
not an ideal solution though

T2 is a development environment. The Tiny Core repository is a store for programs. The two are not the same.

It is a bit beyond my understanding as well but I believe T2 holds core packages that are used to build a Linux system. Puppy has been using T2 for ages and you would know about it if you followed the development process. To be honest, it is not something a user HAS to know unless they are keen on the development background.

Core packages are really that - core packages. They can be binary files or they can be source code which you compile for your specific platform. T2 can be used for other platforms as well as Linux. Users would not normally add such files because they would have to (posssibly) compile stuff as well as deal with all the questions of where in the linux file system to store the files and how to modify the distro specific launcher menu to access the new files.

Once you have your distribution then users may add additional programs. It is not normal to go to T2 to get programs but I suppose they could if they knew what they are doing. More likely you got a repository and load a .deb, .rpm, .pet, .sfs, ... file. When you load such a file via the distro's 'add new programs' tool it will automagically unpack the binaries put them in the right place and alter any menus accordingly.

Debian or Dpup users can get programs from the Debian repository. UPup or Ubuntu users can use the Ubuntu repository.

Puppy 4.4 users can use pet packages and sfs packages from wherever they may be found as well as the official store pointed to by Petget (?).

Because of jrb's work on the sfslinker project, Puppy users can now install programs from the Tiny Core repository as if they were sfs files. I believe Puppy 4.4 includes the sfslinker stuff from jrb and the menu item linking to the Tiny Core repository is there for that reason - nothing to do with the repository used to build the original Puppy 4.4.Last edited by ICPUG on Tue 02 Mar 2010, 09:03; edited 1 time in total

It is correct that Puppy 4.0 and many others are built by T2 but it is also correct to say like me tried to say.

Dpup can make use of Debian repository by going to Package manager and there click on such and they get included.

Upup take them instead from Ubuntu repository
and

This pup we talk about now

Puppy 4.4 CE does have the text in the menu that users can take some files from TinyCore respository. That is what it does say. And what my confused reference to Dpup and Upup was all about. Sorry if it was confusing!

so both of us are correct. I had no clue on what T2 was but I was correct about Pup 44 CE does have such a menu button that activate such access to a TCZ but maybe some script make them into sfs I don't know.

But to me that makes it almost a Tpup in that it can take from TinyCore.

Maybe it has access to many other resources too but although my text was very confused it had truth in it even if my wording may mislead some. the menu button me talked about is still there._________________I use Google Search on Puppy Forum
not an ideal solution thoughLast edited by nooby on Tue 02 Mar 2010, 09:23; edited 1 time in total

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