Developer Tools GUI
Hello,
As stated above, this tool is intended to help new users "get their feet wet"
If you are used to the commands, you prob have a few scripts lying about to do this stuff anyhow...
Remember, the CLI isnt your enemy, but instead a willing and helpful friend. Ask him how, he will tell you..
Wanna know how, for example, "tar" works, ask your friend, the CLI..
Forget xarchive its a PITA anyhow..
In the directory where you D/L the tarball,
open a terminal and copy and paste this:
DevTools is an AppRun, so you will see an icon appear in the directory.
Click it..
Then you can use it to pack/unpack in the future..
As stated above, this tool is intended to help new users "get their feet wet"
If you are used to the commands, you prob have a few scripts lying about to do this stuff anyhow...
Remember, the CLI isnt your enemy, but instead a willing and helpful friend. Ask him how, he will tell you..
Wanna know how, for example, "tar" works, ask your friend, the CLI..
@Nooby, CLI Lessontar --help
Forget xarchive its a PITA anyhow..
In the directory where you D/L the tarball,
open a terminal and copy and paste this:
Then hit enter...tar -xvf DevTools.tar.gz
DevTools is an AppRun, so you will see an icon appear in the directory.
Click it..
Then you can use it to pack/unpack in the future..
Close the Windows, and open your eyes, to a whole new world
I am Lead Dog of the
Puppy Linux Users Group on Facebook
Join us!
Puppy since 2.15CE...
I am Lead Dog of the
Puppy Linux Users Group on Facebook
Join us!
Puppy since 2.15CE...
Ok, so I was wrong in my assumption. For that, I apologize.
I tried using it to make an iso of the contents of a 4gig autorun flash drive and did not get very far as some puppy files were not found.
I ended up using Pburn to burn a DVD data mode with the contents of the USB flash drive.
I also learned that links to an external source have to be absolute and not relative.
I tried using it to make an iso of the contents of a 4gig autorun flash drive and did not get very far as some puppy files were not found.
I ended up using Pburn to burn a DVD data mode with the contents of the USB flash drive.
I also learned that links to an external source have to be absolute and not relative.
puppyluvr - please don't stop working on this. I am trying to understand how the compile process works. I would like to compile from source. Also be able to change entries posted as tar.xxxxxx to pet files so hopefully they will be installed to proper location.puppyluvr wrote: Hello,
As stated above, this tool is intended to help new users "get their feet wet"
If you are used to the commands, you prob have a few scripts lying about to do this stuff anyhow...
Remember, the CLI isnt your enemy, but instead a willing and helpful friend. Ask him how, he will tell you..
I vote for your continued support of this thread and look forward to more good stuff from you.
majorfoo
Hello,
Still around, just been preoccupied by the so called "real world" ..LOL
The other parts of the program are simple scripts..
The compiling is handled by amigo`s src2pkg, which I need to make time to learn more about..
Actual compiling via the cli is much easier than making a gui that does it "automagically"...
As for tar to pet conversion..
tar xvf "something".tar.gz
will create directory "something"
dir2pet "something"
will then turn it into a .pet
dir2pet will create a menu entry and a specs file...
Been working 7 days a week to keep afloat...
Puppy time, as with all "me time" is at a premium ATM...
I may slow down, but I aint stopping...
I have several things "in the fire" that I will be updating ASAP,
including this one...
As Catdude says.... Keep the faith....
Jay..
Still around, just been preoccupied by the so called "real world" ..LOL
The other parts of the program are simple scripts..
The compiling is handled by amigo`s src2pkg, which I need to make time to learn more about..
Actual compiling via the cli is much easier than making a gui that does it "automagically"...
As for tar to pet conversion..
Ex..tar xvf *.tar.gz
dir2pet *
tar xvf "something".tar.gz
will create directory "something"
dir2pet "something"
will then turn it into a .pet
dir2pet will create a menu entry and a specs file...
Been working 7 days a week to keep afloat...
Puppy time, as with all "me time" is at a premium ATM...
I may slow down, but I aint stopping...
I have several things "in the fire" that I will be updating ASAP,
including this one...
As Catdude says.... Keep the faith....
Jay..
Close the Windows, and open your eyes, to a whole new world
I am Lead Dog of the
Puppy Linux Users Group on Facebook
Join us!
Puppy since 2.15CE...
I am Lead Dog of the
Puppy Linux Users Group on Facebook
Join us!
Puppy since 2.15CE...
I tried your Developer Tools application and used xscreensaver-5.14.tar.gz in my experiment. I d/l src2pkg-2.5-noarch.pet as instructed, installed it and ran your app.puppyluvr wrote: As for tar to pet conversion..
Ex..tar xvf *.tar.gz
dir2pet *
tar xvf "something".tar.gz
will create directory "something"
dir2pet "something"
will then turn it into a .pet
dir2pet will create a menu entry and a specs file...
.
It worked flawlessly - it created xscreensaver-5.14-i486-1.pet which installed without any problems and did not need any dependencies.
It has 197 screensavers, 185 work and 12 do not. The 12 that do not work need a font that I don't have on my current install.
This is a great tool to create pet from source with very few keystrokes from user.
I am very happy with the results of this test.
Next I tried your instructions above to create a pet using dir2pet.
A pet was created and when I tried to install, the results were a disaster. Guess it all depends on what you are using in the directory that you are creating pet from.
Anyway, one out of two is not bad for me.
Thanks for providing and look forward to your refinement of the application.
majorfoo
majorfoo, what package were you trying to convert into a pet? I'm just curious becuase I've never encountered that problem, albeit I have been using linux for less than a year.majorfoo wrote:
Next I tried your instructions above to create a pet using dir2pet.
A pet was created and when I tried to install, the results were a disaster. Guess it all depends on what you are using in the directory that you are creating pet from.
If you are in a frugal install, make sure that you unpack the tar.gz files inside of the linux filesystem and not in a Windows file system, or the permissions of the extracted files will get messed up. I usually make a folder named /tmp/pet and do the work from there. Now that I think about it, I should just get puppy to create a /tmp/pet folder on startup.
Clarification: I meant the linux file system in the frugal install; no need to do a full puppy install.