Dotpup making script
Dotpup making script
This script creates dotpups for you, with an integrated simple "un-installer"
Your application will be installed to /usr/local
usage:
Create a new folder, for example "xclock", and copy "make.sh" and "dotpup.sh-template" there.
Also copy there the folder you want to add to your dotpup.
Just this 1 folder, or the script will not work (it can contain subfolders, off course).
If it is a folder called "xclock-01" containing a file "xclock", you should have these files:
/xclock/make.sh
/xclock/dotpup.sh-template
/xclock/xclock-01/xclock
Now run "./make.sh".
Then you will have your "xclock-01.pup".
Mark
Your application will be installed to /usr/local
usage:
Create a new folder, for example "xclock", and copy "make.sh" and "dotpup.sh-template" there.
Also copy there the folder you want to add to your dotpup.
Just this 1 folder, or the script will not work (it can contain subfolders, off course).
If it is a folder called "xclock-01" containing a file "xclock", you should have these files:
/xclock/make.sh
/xclock/dotpup.sh-template
/xclock/xclock-01/xclock
Now run "./make.sh".
Then you will have your "xclock-01.pup".
Mark
Last edited by MU on Mon 05 Sep 2005, 20:15, edited 2 times in total.
Version 02: Fixed a bug (template was missing)
Adapted the script to install packages to /usr/local due to Barrys new directive:
http://www.murga.org/%7Epuppy/viewtopic.php?t=2094
Adapted the script to install packages to /usr/local due to Barrys new directive:
http://www.murga.org/%7Epuppy/viewtopic.php?t=2094
Last edited by MU on Mon 05 Sep 2005, 18:55, edited 1 time in total.
Version 03
Fixed bugs and added more error-handling.
The script also can be used to create dotpups, that can be installed/uninstalled on other Distributions.
You simply have to rename the .pup to .zip after creation, and run "dotpup.sh" after extraction of the zip (works fine on Linux-Mandrake 9.2)
You now also will be asked, if the temporary files shall be deleted.
Mark
Fixed bugs and added more error-handling.
The script also can be used to create dotpups, that can be installed/uninstalled on other Distributions.
You simply have to rename the .pup to .zip after creation, and run "dotpup.sh" after extraction of the zip (works fine on Linux-Mandrake 9.2)
You now also will be asked, if the temporary files shall be deleted.
Mark
Last edited by MU on Wed 07 Sep 2005, 00:47, edited 1 time in total.
Keep going...
Yes, keep your updates going. One day someone will just have the time to prepare a dotpup...
(I've been trying to set time aside to make a pup for easy web publishing in Xampp - by Guestoo - but alas, still trying.)
(I've been trying to set time aside to make a pup for easy web publishing in Xampp - by Guestoo - but alas, still trying.)
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
Raffy,
I think my script would not help you with Xampp.
My script just will help you, if all your files go in 1 folder, for example
/usr/local/Xampp
But I think Xampp has a more complex filestructure?
On other systems, perl goes to /usr/bin /usr/lib and so on.
Apache saves configurations in /etc and so on.
This even differs on the distribution.
To write an installer for files spread all over the filesystem is more complicated, especially if iit shall be able to uninstall these files again.
First, you had to keep a list with all these files.
Then you would have to check somehow (how?), if a library is not needed by another program.
But if you have got something working, I might like to try to help to find a solution
Mark
I think my script would not help you with Xampp.
My script just will help you, if all your files go in 1 folder, for example
/usr/local/Xampp
But I think Xampp has a more complex filestructure?
On other systems, perl goes to /usr/bin /usr/lib and so on.
Apache saves configurations in /etc and so on.
This even differs on the distribution.
To write an installer for files spread all over the filesystem is more complicated, especially if iit shall be able to uninstall these files again.
First, you had to keep a list with all these files.
Then you would have to check somehow (how?), if a library is not needed by another program.
But if you have got something working, I might like to try to help to find a solution
Mark
This is just a reminder for me:
http://www.goosee.com/puppy/development ... gement.htm
The current version of my script does not register anything to pup-get as it uses its own simple uninstaller.
I think I should add that (optionally?), so you can use pup-get to uninstall the dot-pups.
This may take some days.
Mark
http://www.goosee.com/puppy/development ... gement.htm
The current version of my script does not register anything to pup-get as it uses its own simple uninstaller.
I think I should add that (optionally?), so you can use pup-get to uninstall the dot-pups.
This may take some days.
Mark
Didn't someone post the code for this back in July?MU wrote:This is just a reminder for me:
http://www.goosee.com/puppy/development ... gement.htm
The current version of my script does not register anything to pup-get as it uses its own simple uninstaller.
I think I should add that (optionally?), so you can use pup-get to uninstall the dot-pups.
This may take some days.
Mark
Nathan I think?
Perhaps you could borrow what he has done and shared?
doc
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Yes, if you want users to be able to use PCCC to move your dotpup to CD, it must be registered with the pupget manager. It's pretty easy to do, just a few lines of code. ...well maybe more if there are lots of files.edoc wrote:Didn't someone post the code for this back in July?MU wrote:This is just a reminder for me:
http://www.goosee.com/puppy/development ... gement.htm
The current version of my script does not register anything to pup-get as it uses its own simple uninstaller.
I think I should add that (optionally?), so you can use pup-get to uninstall the dot-pups.
This may take some days.
Mark
Nathan I think?
Perhaps you could borrow what he has done and shared?
doc
The key file is /root/.packages/mydotpup.files, which lists all installed files -- PCCC can use this to move all the files to CD.
The other thing that you have to do is append a line onto /root/.packages/alienpackages.txt.
-- the web pages give example code to do it.
Thanks Barry.
I tried to implement all this.
Now the user has the choice to register the package to PupGet.
A small infotext for this can be displayed.
After installation, the new folder is opened in rox
Usage as described in the first message.
Still, it can install just 1 folder.
Mark
I tried to implement all this.
Now the user has the choice to register the package to PupGet.
A small infotext for this can be displayed.
After installation, the new folder is opened in rox
Usage as described in the first message.
Still, it can install just 1 folder.
Mark
Last edited by MU on Wed 07 Sep 2005, 00:47, edited 1 time in total.
Version 05
This one now lets you select an executable with a fileselector in the folder you want to pack.
This executable will automatically be added to Puppy-wxB-menue.
If you add an "icon.xpm" to your folder, the menue will use it.
You can test it with "Month-Calendar":
http://www.murga.org/~puppy/viewtopic.php?t=2026#12529
or with "run2windows"
http://www.murga.org/~puppy/viewtopic.p ... t=15#12748
I just updated them with the new installer, but for run2windows I did not add an icon yet.
wxB-Menue you will find here:
http://www.murga.org/~puppy/viewtopic.php?t=1985
Currently, the installer just adds Menue-entries, but does not remove them if you uninstall the package.
So the user must do it manually using the included grafical menue-editor.
Mark
This one now lets you select an executable with a fileselector in the folder you want to pack.
This executable will automatically be added to Puppy-wxB-menue.
If you add an "icon.xpm" to your folder, the menue will use it.
You can test it with "Month-Calendar":
http://www.murga.org/~puppy/viewtopic.php?t=2026#12529
or with "run2windows"
http://www.murga.org/~puppy/viewtopic.p ... t=15#12748
I just updated them with the new installer, but for run2windows I did not add an icon yet.
wxB-Menue you will find here:
http://www.murga.org/~puppy/viewtopic.php?t=1985
Currently, the installer just adds Menue-entries, but does not remove them if you uninstall the package.
So the user must do it manually using the included grafical menue-editor.
Mark
Last edited by MU on Wed 07 Sep 2005, 02:31, edited 1 time in total.
Version 06
It allows you to add the loacation of configuration-files (for example /root/.myapp.rc) to a text-file "config.files".
These lines will be added to PupGet if the user chooses to register the application to it.
See readme.txt
Detailed description of this point:
http://www.murga.org/%7Epuppy/viewtopic ... t=15#12764
Mark
It allows you to add the loacation of configuration-files (for example /root/.myapp.rc) to a text-file "config.files".
These lines will be added to PupGet if the user chooses to register the application to it.
See readme.txt
Detailed description of this point:
http://www.murga.org/%7Epuppy/viewtopic ... t=15#12764
Mark
- Attachments
-
- dotpup-maker-script-mu06.pup
- (8.53 KiB) Downloaded 1001 times
The further usage of this script is depreciated (this means: please do not use it any further).
There is a better version, with an additional grafical interface:
http://www.murga.org/%7Epuppy/viewtopic.php?t=2138
I'll leave version 06 online for documentation-purposes only.
Mark
There is a better version, with an additional grafical interface:
http://www.murga.org/%7Epuppy/viewtopic.php?t=2138
I'll leave version 06 online for documentation-purposes only.
Mark