I am currently setting webmin, usermin and virtualmin applications (plus a few other administration packages when it's all up) for a "web administrators" package for puppy.
I can't seem to find any guide to a set of locations for the packages and their libraries, etc.
Can someone assist with a pointer to a message or the default standards used for puppy please.
Id rather not worry Barry yet if others can help, he's got enough on his plate.
thanks in advance
scsijon
Where do I put it : or: new puppy application locations
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
pm raffy
or email at raffymn [at] yahoo . com
tell us a little more of what you are doing
this might be helpful
http://www.puppylinux.com/development/p ... tement.htm
or email at raffymn [at] yahoo . com
tell us a little more of what you are doing
this might be helpful
http://www.puppylinux.com/development/p ... tement.htm
Thanks i have sent raffy a pm.
What i'm looking at, is building an web administration set of packages with the idea of a totally portable system. Currently I look after an area of about 400km. and a number of owners, multiple configurations, etc. I'd like to have a cd to walk in with and boot on one of their workstations to do what I want to rather than part at my site and the rest on theirs.
As a second part (later) is to create a ?secure intranet website on puppy for them rather than m$
What i'm looking at, is building an web administration set of packages with the idea of a totally portable system. Currently I look after an area of about 400km. and a number of owners, multiple configurations, etc. I'd like to have a cd to walk in with and boot on one of their workstations to do what I want to rather than part at my site and the rest on theirs.
As a second part (later) is to create a ?secure intranet website on puppy for them rather than m$
package by package
It's the usual locations in Linux: programs go to /usr and libs go to /lib or /usr/lib. Some people use /usr/lib for applications, most others use /usr/local.
Any changes that you make will be saved in pup_save, so make sure pup_save is saved in hard disk (in ext2 or fat32 partition will be good, not ntfs).
Please focus first in getting your system working on a package by package fashion. Tip: see /initrd/pup_rw for changes to your system - you can copy a snapshot of changes and put in /package1, /package2, as you add packages. Do this as soon as the package begins working.
Any changes that you make will be saved in pup_save, so make sure pup_save is saved in hard disk (in ext2 or fat32 partition will be good, not ntfs).
Please focus first in getting your system working on a package by package fashion. Tip: see /initrd/pup_rw for changes to your system - you can copy a snapshot of changes and put in /package1, /package2, as you add packages. Do this as soon as the package begins working.
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
AFAIK, Barry's never said what file layout standards Puppy should use. The structure above is conventional in most Linux distros, but badly flawed.raffy wrote:It's the usual locations in Linux: programs go to /usr and libs go to /lib or /usr/lib. Some people use /usr/lib for applications, most others use /usr/local.
In particular, it puts the files needed by an application all over the place, in a number of different directories, making it very difficult to deal with applications as a unit (especially if you want to allow easy and correct access to multiple versions of the same application.)
One of the things I just discovered about ROX is that it takes a different approach to solve this difficult problem. See the "Application Directories" section at http://rox.sourceforge.net/desktop/about_rox?. (There are other ways - we developed some at Chevron, but ROX is much simpler to implement, as the other methods I've seen rely on both scarily complex automounter maps and the name/directory services that drive them.)
The ROX approach allows apps to remain easily "packaged", even after installation in the filesystem - deleting an app is just deleting its directory. Although I haven't tried it on Puppy yet, this lets ROX support ZeroInstall, which should allow drag-and-drop app installation (does this work with PETs? Another thing I haven't tried...)