I've had lots of fun installing some apps with Puppy. There are lots of great pups and pets to choose from.
That's a good thing, what I don't like is that it looks rather easy installing apps or libraries that could kill my installation.
I wanted to install aMule and needed a library for it so I installed a version of wxgtk (or gtk) that totally ruined my system. Right now I have issues with Xine (out of sync) that also could be started because of something I previously installed.
Is there a way of knowing what I can install without any problems on my 2.15CE install? I would be nice to trust the apps I'm choosing.
It looks like the repositories Puppy uses are for all Puppy versions, and I don't know it they are always compatible. Mostly there is no installationguide or extra information.
How to tell which software works with my Puppy?
-
octobclrnts
- Posts: 35
- Joined: Sun 15 Apr 2007, 06:48
If you chose to do a full HD install, there isn't a pup_save file so don't frustrate yourself looking. I'm not sure which is your situation, just thought I'd point that out.
Puppy [color=green]2.17[/color]
HP Pavillion [color=green]dv1000[/color]
Ram [color=green]512MB[/color]
Proc [color=green]1.5GHz Pentium M[/color]
HP Pavillion [color=green]dv1000[/color]
Ram [color=green]512MB[/color]
Proc [color=green]1.5GHz Pentium M[/color]
I've suggested an auto. downloader for libraries, modules, & codecs.
This would free the users from having to look for all this themselves.
Also Puppy would be much smaller because it'd have a minimum of stuff.
Just enough to allow Puppy to boot & then download only what's needed.
For off-line uses an additional file (like zdrv_xxx.sfs) would be available.
So the downloader would source libraries from the web & a local file.
This may be moot soon, on-line apps. are all the rage now a days.
So why not on-line Operating Systems? Don't download... Boot!
With the OS & the apps. on-line, there's no downloading needed,
except for media (data) which is the only true download.
This would free the users from having to look for all this themselves.
Also Puppy would be much smaller because it'd have a minimum of stuff.
Just enough to allow Puppy to boot & then download only what's needed.
For off-line uses an additional file (like zdrv_xxx.sfs) would be available.
So the downloader would source libraries from the web & a local file.
This may be moot soon, on-line apps. are all the rage now a days.
So why not on-line Operating Systems? Don't download... Boot!
With the OS & the apps. on-line, there's no downloading needed,
except for media (data) which is the only true download.
-
Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
additional software
from the menu in 2.15
Start(menu) Setup / setup puppy / Puppy package manager
the most reliable options are the first (maintained by Barry)
it used to be followed by Senior Developer GuestToos dotpups
however even something like
gosh I miss those penguins . . .
I would suggest that the forum thread "additional software" on the forum is probably the most up to date method of finding and installing at present
the page links here and on the default 2.15 home page
http://puppylinux.org/wikka/
are heavily maintained (again some links need updating)
then there are the collections (sfs files)
and on line programs
http://puppylinux.org/wikka/Puppy215WebApps
and MU.s depository . . .
http://puppyfiles.org/dotpupsde/dotpups/
Yes too much choice is not always a good thing . . .
Start(menu) Setup / setup puppy / Puppy package manager
the most reliable options are the first (maintained by Barry)
it used to be followed by Senior Developer GuestToos dotpups
however even something like
is linking to old forum linksXpenguins∞ (218k)... little penguins that walk on your desktop ... Home Page
gosh I miss those penguins . . .
I would suggest that the forum thread "additional software" on the forum is probably the most up to date method of finding and installing at present
the page links here and on the default 2.15 home page
http://puppylinux.org/wikka/
are heavily maintained (again some links need updating)
then there are the collections (sfs files)
and on line programs
http://puppylinux.org/wikka/Puppy215WebApps
and MU.s depository . . .
http://puppyfiles.org/dotpupsde/dotpups/
Yes too much choice is not always a good thing . . .
-
Bruce B
T_B, if you weren't feeling a bit lost - something would be wrong with you.
I'd describe Puppy's package managment as a WIP, (Work In Progress)
Lots of packages, how will you know if you like or want them? By installing them.
What's a good way to mess up your Puppy installation? By indiscriminately installing lots of packages, from a variety of sources.
I'd say install as many as you please. Discover your favorites. Be willing to set Puppy up again. Then just install your favorite ones that work well for you.
I'd describe Puppy's package managment as a WIP, (Work In Progress)
Lots of packages, how will you know if you like or want them? By installing them.
What's a good way to mess up your Puppy installation? By indiscriminately installing lots of packages, from a variety of sources.
I'd say install as many as you please. Discover your favorites. Be willing to set Puppy up again. Then just install your favorite ones that work well for you.
Bruce B; Good advice, the SAVE file is the only thing that changes,
another words... it's the only writable Puppy file, the rest are read-only.
Idea: How about the Puppy package installer offering to make a backup copy
of the SAVE file just before installing any type of package at all?
This would help a whole lot & would have saved several of the current posts.
another words... it's the only writable Puppy file, the rest are read-only.
Idea: How about the Puppy package installer offering to make a backup copy
of the SAVE file just before installing any type of package at all?
This would help a whole lot & would have saved several of the current posts.
Thanks for all the answers guys. I'm still lost, but now I know I'm not alone 
Would help a great deal if there were more up-to-date instructions with the pups or pets. A small txt file with the same name as the pup providing some info would be enough imo. Amule is a good example, there is a htm file that links to the forum with a great how-to install (I didn't read that the first time I tried to install it)
Would help a great deal if there were more up-to-date instructions with the pups or pets. A small txt file with the same name as the pup providing some info would be enough imo. Amule is a good example, there is a htm file that links to the forum with a great how-to install (I didn't read that the first time I tried to install it)
... no, you'r not... On Puppy versions: all dotpups should be upward compatible. Most new users have v2.00 or higher, so any dotpup should work fine as we all have very similar systems.Thanks for all the answers guys. I'm still lost, but now I know I'm not alone Smile
Amule is kind of a special case. Handling the wx library can be tricky. Did you know that most packages can be un-installed by Puppy's own package manager ? Anyway it is a good idea to copy the pup_save-file (in /mnt/home ) to a save place once a while. I personally never had any problems with dotpups, exept for amule which did not work in puppy versions > 2.13.
greetings,
fudgy
Xpenguins would be here: http://www.murga-linux.com/puppy/viewto ... ?p=282#282
but it seems to have been removed ... i have an xpenguins.pup file on my hard drive
most of my dotpup packages install files in my-applications ... so Puppy should leave the files alone when you upgrade Puppy, and if a newer file, for example a library file, is in /bin, /sbin, /lib, /usr etc etc etc, Puppy should use the newer file rather than the file in my-applications ... so my packages try to not interfere with the operating system if possible
i try to make packages which are as self contained and as separate from Puppy as possible (as opposed to integrating with Puppy ... i try to avoid integrating with the operating system as much as possible ... i am happy if my packages do not damage the operating system, and if the operating system leaves my packages alone)
but it seems to have been removed ... i have an xpenguins.pup file on my hard drive
most of my dotpup packages install files in my-applications ... so Puppy should leave the files alone when you upgrade Puppy, and if a newer file, for example a library file, is in /bin, /sbin, /lib, /usr etc etc etc, Puppy should use the newer file rather than the file in my-applications ... so my packages try to not interfere with the operating system if possible
i try to make packages which are as self contained and as separate from Puppy as possible (as opposed to integrating with Puppy ... i try to avoid integrating with the operating system as much as possible ... i am happy if my packages do not damage the operating system, and if the operating system leaves my packages alone)
-
Bruce B
If you have any time invested in the existing save file, that would be the best way to approach it.sunburnt wrote:Bruce B; Good advice, the SAVE file is the only thing that changes,
another words... it's the only writable Puppy file, the rest are read-only.
Idea: How about the Puppy package installer offering to make a backup copy
of the SAVE file just before installing any type of package at all?
This would help a whole lot & would have saved several of the current posts.
1) Copy the existing pup_save to a different name
2) Use the original for R&D
3) When R&D is done, delete the original
4) Rename the backup to its original name
5) Install the packages you really like and want to keep