Puppy Linux Discussion Forum

[01micko]

Hi folks,

New version, 20101229, handles txz better

With the advent of "Woof - The Puppy Builder" there has been a pack of different Puppy's with different lineages crossbreeding.

Prime examples are Lupu Puppy 5, the Luci development for 5.1 and Barry's Spup Slackpup betas.

One problem.. the actual Puppy repos particular to those 'wooflets' are barish, though the Luci repo is starting to look healthy.. and the tool described here is a small part of that.

alien2puppy is a command line based tool to get a main app and it's dependencies 'merged' into a puppy package, either sfs or pet.

What you do is, plonk the app and all the dependencies in a single working directory, for big apps, do this outside your pupsave. Then you invoke the script in that directory with:

[don570]

Worked great for me. Instructions were clear.
I made Audacity and Abiword pet packages out of
debian packages in only couple of minutes.
Great stuff!!

To compare with old method of making pet packages see
http://www.murga-linux.com/puppy/viewtopic.php?t=55740&start=690
---------------------------------------------------------------------------------------------

[don570]

I wanted to show how easy it was to use alien2puppy
so I wrote a tutorial located here

I used Audacity as the example but lots of other application packages
can be built using this procedure.

EDIT: I wrote another tutorial this time for building Abiword here

____________________________________________________________________

[01micko]

Thanks don570

I'll put a link to that in the first post, near where I say that there's no "man" page.

Cheers

[don570]

I have discovered one flaw in alien2puppy.
I made the mistake of using a pupsave file that was
very small, therefore there was little space in filesystem for the new
pet package to form.

My recommendation is to make sure that there is at least 20 mb of free
space to let the pet package be created. Unfortunately there
is no warning at terminal so the user can become confused.

[gcmartin]

dm570 hit an issue where a check in the alien2puppy tool could be improved on

On this space finding, would it be prudent to put a "test" at the beginning of the alien2puppy script to see if there is 20MB, then warn the user?

It it helps make a better user experience, it may be worth considering.

[don570]

Recently I have been building my pets on a partition that has lots of space.
This way I avoid the 'lack of space problem'
I originally had been building in /root which is probably a bad practice.

___________________________________________________

[don570]

I describe how to make Audacity 2.0.4 alpha from nightly build...

http://www.murga-linux.com/puppy/viewtopic.php?p=697808#697808

Just a note... I am finding when constructing SFS packages that
I must move libraries to /usr/lib/ from /usr/lib/i386-linux-gnu

Pet packages don't have this problem.

___________________________________________________________

[don570]

I made a gettext version of alien2puppy 0.2

I changed some of the wording slightly and
I put a warning if the folder name has blank spaces.

I included a pot file if that will help the translators.

Instructions: put script 'alien2puppy' in executable path.

__________________________________________

[rodin.s]

I have made Russian translation.
Run this in terminal to make it work:

[don570]

I put alien2puppy in my right click utility package for convenience.
I'll put Russian mo file inside as well.
_________________________________________

I described how I made audacity 2.1 (daily build) with alien2puppy

http://www.murga-linux.com/puppy/viewtopic.php?p=817377#817377

__________________________________________

I found that I had to remove several libraries that I found in i386 folder
and put these in regular /usr/lib/ folder

_____________________________________

[gcmartin]

What does it take to have this utility included in future PUPs built via WOOFCE?

[don570]

I found that one of the audacity effects crashs when it is used.

Sliding time scale/pitch shift


That is the problem when using the daily build.

..But it works great otherwise.

[LazY Puppy]

Just tried this to check out, if it can handle the i386-linux-gnu directory (which is used in Precise and needs to be turned into a symbolic link). I've tested having alien2puppy extracted to /root/Downloads and executed from this location.

Tested with these files inside of directory, /root/Desktop/Aqualung_0.9-beta11-precise:

aqualung_0.9~beta11-1ubuntu9_i386.deb
libifp4_1.0.0.2-5_i386.deb
libjack-jackd2-0_1.9.8~dfsg.1-1ubuntu2_i386.deb
liblrdf0_0.4.0-5build1_i386.deb
liblua5.1-0_5.1.4-12ubuntu1_i386.deb
libmodplug1_0.8.8.4-1_i386.deb
liboggz2_1.1.1-1_i386.deb
libraptor1_1.4.21-7ubuntu0.1_i386.deb
libwavpack1_4.60.1-2_i386.deb

Command used in a Terminal:

/root/Downloads/alien2puppy -s /root/Desktop/Aqualung_0.9-beta11-precise

Didn't work!

Terminal Output:

Please wait a moment while /root/Desktop/Aqualung_0.9-beta11-precise is populated
The type of files can't be determined

What's wrong here?

---

Edit:

At least it doesn't have any i386-linux-gnu related code, so it obviously can NOT handle new .deb files from multi arch distros like Ubuntu.

PaDS 1.0.4 has the code and so it can do this!

Though, of course that's not the cause for the above mentioned problem...

[don570]