dpupmaker.sh v1.9 -- compiles source tarballs into Dotpups

[MU]

cd chimera
./chimera

Or use the absolute path:
/root/downloads/chimera/chimera

You can click it , too in rox.
But it does not display dotpups.de , seems to have problems with CSS.
Mark

[bugman]

Oh, I'd figured out the click on the binary in Rox bit, it's just the typing it in xrun that flummoxed me at first. And I've got it working from the jwm menu as well.

It's interesting that you said to "cd chimera" even though the "chimera" folder is inside another ("chimera-2.0a19"); in DOS that wouldn't work, right? Does Linux find folders within folders without the full path being specified? That doesn't make any sense, there's several folders in different paths with the same name, "bin" being a good example.

Hey Murga, I'm going to start charging myself every time I ask a basic question in here and send you (or Barry) the money at the end of the year, okay? It won't be much (my income is way below the poverty line) but the two of you deserve every penny of it...

[bugman]

MU, thanks much for your help. Sadly though, Chimera is not the answer I was looking for. Maybe the answer is to learn to program (I used to write 6502 assembly in both monitor and hex codes 20 years ago) and add cookies to Dillo myself. If I eat lots of healthy food I may live long enough to get it done...

[MU]

It's interesting that you said to "cd chimera" even though the "chimera" folder is inside another ("chimera-2.0a19");.

No, I assumed you are already in /chimera-2.0a19 for the compilation.
But you can navigate quite fast in the shell with the auto-completition.

cd chim[tab] will show chimera
If there is more than one match, hit[tab] again, to see them all.
Concerning Dillo, please look here:
http://www.murga.org/~puppy/viewtopic.p ... highlight=

[bugman]

That's pretty funny, I have the patched version, so I am getting cookies! Dumb. I had tried it on the used book sites I work through once before and was having problems; I'll have to try and figure out which site it was and why I was asked to log in repeatedly...

But then there's that other problem. Dillo doesn't print either...

[bugman]

And now I'll never have time to read Rute; I'll spend the rest of my days converting a Mozilla bookmark file into a Dillo one...

[MU]

Bookmark-Converter:

search bookmark.html in /root/.mozilla

run this command:

Code: Select all

echo ":s0: test" > /root/.dillo/bm.txt && cat bookmarks.html |grep tp| sed "s/^.*HREF=./s0 /" | sed "s/\"[^>]*>/ /" | sed "s/<.*$//" >>/root/.dillo/bm.txt

In my case it works, in your case maybe you need to remove some corrupted lines with an editor from /root/.dillo/bm.txt, if Dillo does not display the new bookmarks.

Mark

[bugman]

And here I'd started doing it by hand...

Am proud of myself for making my Moz start page (an html page of my most-visited sites) into the Dillo start page, and moving about:splash to the Dillo "home" page by editing /root/dillo/dillo85p a bit. This is so much more fun than w98...

I figured out the cookie thing. I have DSL, with an unpatched Dillo. Must've done the test there. So now my usage of DSL is down to one thing. I can't record through my sound card in DSL, I get a scratchy noise with a very faint bit of the actual sound from the mic. Since I do experimental music, that's actually a good (well, interesting) thing...

Everything else is done in Puppyland!

[bugman]

Hey, it worked, thanks! I had to change the "cat bookmarks.html" to "cat /root/.mozilla blah blah blah...and then the magic happened! I understood a little of what I was typing into xterm and the rest was well...I don't understand why LDA and ROR and DEX and CPY still make so much sense to me and "s/\"[^>]*>/ /" | sed " doesn't...

[jmarsden]

I would like to say that I am a new user and a complete idiot (the total package!) but I like doing stuff in a terminal. I learn things, I feel cool, I get to whine and complain in this forum when nothing works!

Can I suggest reading Eric Raymond's essay How to Ask Questions the Smart Way ? That might help you ask in a way that makes it easier for others to provide good answers.

Do bear in mind that my script was intended for use by people who are used to compiling applications from tarballs... it tries fairly hard to be general, and works much of the time... but it can't compensate for a lack of experience when it doesn't work as you'd expect, I'm afraid!

That being said, I downloaded, unzipped, and ran dpupmaker on the Chimera tarball.

It would have been very helpful for you to state the URL of that tarball, and what exactly you typed at the command line.

Code: Select all

./dpupmaker.sh: line 121: ./configure: No such file or directory dpupmaker.sh: Error: Unable to configure application chimera-2.0a19

This suggests to me that the tarball you have downloaded may not be set up to be compiled using the standard GNU Autotools. Either that, or the directory it unpacks to is not what dpupmaker.sh was expecting, though in that case the error message should have been different.

I checked line 121 and it said:

./configure ${4:-"--prefix=/usr/local"} ||

Should I change this to something else ...

No. The error mesage you see says that there is no script ./configure, so editing what parameters are passed to it isn't going to help.

Is Chimera un-puppable

Someone who understands how to manually compile and install Chimera will be ably to create a .pup of it. Whether dpupmaker.sh can handle whatever idiosyncracies its source tarball may have, is a different question entirely.

Should I put aside a week and read the f'ing Rute manual?

No, just start reading it, and read a little more of it each week... reading it all in one go probably will just confuse you But reading it, or any good Linux tutorial, is a good idea if your aim is to gain competence at a shell prompt.

I just found the tarball I think you are using, at http://www.rocklinux.net/people/ripclaw ... a19.tar.gz . It uses an older approach to creating its Makefiles, an Imakefile and xmkmf. If you unpack it and look at chimera-2.0a19/doc/INSTALL you will see the instructions on how to build it. Sadly, even they don't quite work on Puppy, they use a tool called gccmakedep which isn't provided (and which I have not heard of before). Or else my Puppy is different from MU's, since he seems to have compiled the thing OK!

Overall, I'm not sure it is worth adding extra complexity to dpupmaker.sh to try to handle the oddball cases of older non-GNU-Autotools-using tarballs. It's "enough", in my opinion, to just let the user of the script know that there was no ./configure script, so dpupmaker.sh can't continue... and it did exactly that for you. And, of course, others have written helpers for packagers who compile things and then want to make a package of the results. dpupmaker.sh is not the "only game in town".

Jonathan

PS. My first personal computer was 6502-based, hand assembled from a kit, with 1 and 1/4 K of RAM... a hex keypad to enter code and data, and a cassette interface I never did get to work right

PPS Wrote this, and then saw the MU had already followed much of this path with you... oh well!

[jmarsden]

A new version of dpupmaker.sh has just been released (updated in the first post of this thread). It now searches all of /usr for installed files rather than just /usr/local, and has a fix to allow it to compile Samba tarballs. The changelog now reads:

Code: Select all

# $Log: dpupmaker.sh,v $
# Revision 1.9  2006/03/05 05:31:32  root
# Search /usr for installed files not just /usr/local
#
# Revision 1.8  2006/03/04 01:52:07  root
# Added support for Samba-style source tarballs.
#
# Revision 1.7  2006/03/04 01:50:25  root
# Added support for .tgz file extension.
#
# Revision 1.6  2006/01/13 09:07:51  root
# Source code now installed in /usr/local/archive
# Fixed size calculation for source dotpups
# Fixed registration of source dotpups with pupget database
#
# Revision 1.5  2006/01/13 05:34:19  root
# Removed make distclean as it is no longer a common target.
# Check exit status of ./configure command and exit upon failure.
# Include dpupmaker.sh version in created dotpup.sh files.
# Add creation of "source dotpup" files (experimental new feature).
#
# Revision 1.4  2006/01/03 10:26:02  root
# Added a version number based on RCS Id which is displayed before usage info.
# Added a simplistic check that development tools have been installed (which make).
# Fixed a bug affecting packages with dirs inside their structure with the same
#   name as the tarball (such as binutils).
# Added missing extra backslashes in the embedded dotpup.sh template.  JM.
#
# Revision 1.3  2006/01/03 03:57:06  root
# Added ability to override options passed to ./configure as a fourth parameter.  JM.
#
# Revision 1.2  2006/01/02 11:03:41  root
# Added GNU GPL Copyright notice prior to initial publication.  JM.
#
# Revision 1.1  2006/01/02 09:14:56  root
# Initial revision

Jonathan

[MasterK]

Just want to say Great script!
i've just managed to create my own Proftpd pup package . I've used this FTP server daemon for quite a while, so i was happy to see this one compiling without the big problems.

One minor hassle was the options settings for dpupmaker, which took me a couple of "tryouts" before i got it right.
Proftpd compiles with mod_ldap which isn't included in the pup developer package, so i had to --disable-mod-ldap in the configure script.

Using dpupmaker the correct syntax for this is:

./dpupmaker.sh proftpd-1.2.10.tar "This is a ftp server daemon" "" "--disable-mod-ldap".

It's IMPORTANT you remember ALL the options in the commandline, i just placed 2 quotationmarks for the empty software group, just using the standard settings.

Again.. Thank you for a great script.

[ELMIT]

I try to make a pup package from realtek-linux-audiopack-3.5-6.tar.bz2

The installation script of this package was:

Code: Select all

#!/bin/sh

######## VERSION 1.0 ########

KERNEL_VER=`uname -r`

echo ".....Decompress Driver source v1.0.9b Rv3.5.6"
tar xvpfj alsa-driver-1.0.9b_26.tar.bz2 > /dev/null 2>&1
echo ".....Decompress ALSA Library source v1.0.9"
tar xvpfj alsa-lib-1.0.9.tar.bz2 > /dev/null 2>&1
echo ".....Decompress ALSA Utility v1.09a"
tar xvpfj alsa-utils-1.0.9a.tar.bz2 >/dev/null 2>&1
#echo ".....Decompress XRealMixer v0.5"
#tar xvpfj xrmix-0.5.tar.bz2 > /dev/null 2>&1
sync

echo "Remove old sound driver"
if [ -d /lib/modules/$KERNEL_VER/kernel/sound ]; then
   rm -rf /lib/modules/$KERNEL_VER/kernel/sound/pci
   rm -rf /lib/modules/$KERNEL_VER/kernel/sound/acore
   rm -rf /lib/modules/$KERNEL_VER/kernel/sound/driver
fi

echo "Compile Driver........"
cd alsa-driver-1.0.9b_26
./configure                 
make
make install
./snddevices 
cd ..

echo "Remove old alsa library"
rm -rf /lib/libasound.*
rm -rf /usr/lib/libasound.*

echo "Compile ALSA Library....."
cd alsa-lib-1.0.9
./configure
make
make install
cd ..


echo "Compile ALSA Utility......"
cd alsa-utils-1.0.9a
./configure
make
make install
cd ..

#echo "Comiple XrealMixer......"
#cd ./

## for x86_64
if [ -d /usr/lib64 ]; then
  cp -l /usr/lib/libasound.* /usr/lib64
fi

## remove driver modules
if [ -f /etc/init.d/alsasound ]; then
   /etc/init.d/alsasound stop
fi

## del audio stat file
if [ -f /etc/asound.state ]; then
   rm -rf /etc/asound.state
fi

## alsa driver sndstat file relink 
rm -rf /dev/sndstat
ln -s /proc/asound/oss/sndstat /dev/sndstat

## sample wave
if [ -d /usr/share/sounds/alsa ]; then
     bzip2 -d test.wav.bz2
     cp -f test.wav /usr/share/sounds/alsa
     rm -rf test.wav
else
     mkdir /usr/share/sounds/alsa
     bzip2 -d test.wav.bz2
     cp -f test.wav /usr/share/sounds/alsa
     rm -rf test.wav
fi

echo "Remove Folder....."
rm -rf alsa-driver-1.0.9b_26
rm -rf alsa-lib-1.0.9
rm -rf alsa-utils-1.0.9a
alsaconf 

# dpupmaker.sh realtek-linux-audiopack-3.5-6.tar.bz2 Realtek-3.5-6
/usr/local/bin/dpupmaker.sh: line 133: ./configure: No such file or directory
dpupmaker.sh: Error: Unable to configure application realtek-linux-audiopack-3.5-6

What do I need to change to get it to work?