big_bass ,Amigo, ttuuxxx chit-chat zone?

[big_bass]

here are some ongoing talks about packages



well umm.......... I confess
I want to just paste a name instead of typing

avoid typos ... ya know

so you can place this script on the desktop
and drag N drop any file onto it and it will strip
away the path name leaving you just the name


if you use rxvt you can
select the text in the box and paste to the terminal


or much better if you use sakura
you get an option to copy
then pasting easier


you can also copy and paste into a text editor too


the screen shot shows I just dragged N dropped that file on top of the "base" script on my desktop and the dialog box opened up and stripped the path from the file name

I use this script many times a day
thought to share even though its simple
but practical

big_bass

[ttuuxxx]

Hi Bigbass

I would rather a tool to strip junk from files, setup the same as that, where I could drag a newly compiled bin or .so file and in the background it runs this command to.

strip -R .note -R .comment filename

that would make me happy, less copy and paste, or even have it as part of the right click menu, strip file
ttuuxxx

[big_bass]

Hi Bigbass

I would rather a tool to strip junk from files, setup the same as that, where I could drag a newly compiled bin or .so file and in the background it runs this command to.

strip -R .note -R .comment filename

that would make me happy, less copy and paste, or even have it as part of the right click menu, strip file
ttuuxxx

well if you read through the base script I already have an example
how to set up a right click in ROX
to do just that an easier way to add small apps to ROX
quickly


try this let me know how it went

big_bass

[amigo]

Joe, that's a bit of overkill creating a temp file. All you need is this:

#/bin/sh
gxmessage `basename $1`

[ttuuxxx]

ok that worked from the command line one I place it in usr/bin and renamed it stripbins <-- saves on the shift underscore thing, I'm real lazy,lol
now to get it working with rox or maybe a drag and drop function.
Man this is going to be a great time saver.
ttuuxxx

[ttuuxxx]

excellent I got it in the rox right click menu and it works yahooooooooooooooooooooooooo
all I do is right click the mouse on a bin file and select at the top of the list 'stripbins' and boom aqualung goes from 2101kb to 764kb in 1 second flat thats so coolllllllll
thanks big bass your the greatest
ttuuxxx

[ttuuxxx]

Hey bigbass or amigo I've been trying to compile this program tonight, its a strict gmake with no configure file, do you know the gmake only command to compile it as i486? It keeps compiling as i686, I've been spending hours on this. reading up etc and nothing.
thanks as always
ttuuxxx

[amigo]

What program is it?
If it ahs no configure routine, you'll need to add the CFLAGS you want to the compile line
CFLAGS = "-O2 -march=i486 -mtune=i686"
Then look for the compile line -something like:
gcc -o prg-name $(OBJS)
Insert CFLAGS in there:
gcc -o prg-name $(CFLAGS) $(OBJS)

[big_bass]

Joe, that's a bit of overkill creating a temp file. All you need is this:

#/bin/sh
gxmessage `basename $1`

I posted to you twice and it disappeared ? strange

Hey Gilbert

less code is always better thanks
for the tips
they are always welcomed
just tried your code snippet nice

and thanks for the recent letter
great info
still working on a reply

Joe

[ttuuxxx]

Hi amigo you asked what I was trying to compile, its cdrtools, I guess I'll work on it in the morning its late now. Thanks for the help bigbass and amigo
ttuuxxx

[big_bass]

Hi amigo you asked what I was trying to compile, its cdrtools, I guess I'll work on it in the morning its late now. Thanks for the help bigbass and amigo
ttuuxxx

this shows what else you'll need to get it running

imagine if all puppy packages had one of those
http://riksun.riken.go.jp/pub/pub/Linux ... SlackBuild

or a "short cut", down load that package as a tgz
there's a note that Debian has errors
with their package on the main page of cdrtools

big_bass

[ttuuxxx]

Hi amigo you asked what I was trying to compile, its cdrtools, I guess I'll work on it in the morning its late now. Thanks for the help bigbass and amigo
ttuuxxx

this shows what else you'll need to get it running

imagine if all puppy packages had one of those
http://riksun.riken.go.jp/pub/pub/Linux ... SlackBuild

or a short cut down load that package as a tgz
there's a note that Debian has errors
with their package on the main page of cdrtools

big_bass

Yes I been talking to the developer of cdrtools about how his gmake (GNU Make) or Smake that he uses is not as user friendly as ./configure - make, like his default was opt/bin/schilly opt/lib etc, you actually have to read about 15+ different how to helps, etc to find out you have to go to /root/cdrtools-2.01.01/DEFAULTS/Defaults.linux and open that up and change the default to /usr , plus that was one out of 43 different documents in that folder, Then once you get that worked out, You can't set it to compile as i486 or i386, I tried different cf flags, i tried changing the gmake, I even installed smake, which is like gmake and tried to change that what a pain, it would of taken like 2 seconds if he had the old ./configure file that worked, he has one hidden in a directory, but that doesn't do anything anyways.
Then end result after 1.5 days trying to get it working is that it compiles perfect as i686 in the right directory, but thats it. I'll try your slackware sources they might be patched.
thanks again Joe
ttuuxxx

[big_bass]

Jeff

ftp://mirror.pacific.net.au/linux/slack ... i486-1.tgz

his default was opt/bin/schilly opt/lib

now that's really "schilly" .....mmm I mean silly

Joe

[ttuuxxx]

Jeff

ftp://mirror.pacific.net.au/linux/slack ... i486-1.tgz

Joe

Thanks joe
But that one is a slackware version and needed 2 libs min, I kind of was building this for 4.2 also and I don't want to mix an match, Sometime slack works on 4 series and sometimes not, but with the heart of a burning program, I better keep it OS specific.
Oh ya the developer just replied to me on how to change it to i486, this is what he said
'Well I did already tell you how to do it....

./configure & make is a very outdated method

If you know how to compile for an ancient CPU, just do what I told you and use
COPTX=
'
ya well I tried looking up the COPTX= thing and still working on it, grrr
Thanks again for our help
ttuuxxx

[amigo]

Okay, try this:
export COPTX="-march=i486 -mtune=i686"
and then run configure and make from the same terminal.
Schilly has a *huge* ego -he kept development on the kernel SCSI/CD system from going forward for years until the kernel devs finally gave up and wrote another interface which lets you burn CD's without scsi emulation. Schilly was also very miffed when the folks at debian forked an earlier version of cdrtools into the cdrkit package. he slammed them a lot on his website(still does9. Unforuntately, even debian was unable to recruit enough developers with enough zeal to work through the problems with cdrkit. Schilly also 'held back' his bule-ray code for quite awhile, but I think he has finally included it in cdrtools. He also has a huge 'beef' with the autoconf devs, so that's why he uses that insane 'smake' that he came up with. I think the config files and scripts constitute a lot more files than the real code.
debian quit using cdrtools because Schilly changed to a non-free license.

[ttuuxxx]

Okay, try this:
export COPTX="-march=i486 -mtune=i686"
and then run configure and make from the same terminal.
Schilly has a *huge* ego -he kept development on the kernel SCSI/CD system from going forward for years until the kernel devs finally gave up and wrote another interface which lets you burn CD's without scsi emulation. Schilly was also very miffed when the folks at debian forked an earlier version of cdrtools into the cdrkit package. he slammed them a lot on his website(still does9. Unforuntately, even debian was unable to recruit enough developers with enough zeal to work through the problems with cdrkit. Schilly also 'held back' his bule-ray code for quite awhile, but I think he has finally included it in cdrtools. He also has a huge 'beef' with the autoconf devs, so that's why he uses that insane 'smake' that he came up with. I think the config files and scripts constitute a lot more files than the real code.
debian quit using cdrtools because Schilly changed to a non-free license.

Yes he doesn't seem to be nice in the emails, I was very polite but he wasn't even close, I tried what you said and it compiled as i686
here some of the output

==> COMPILING "OBJ/i686-linux-gcc/ifo_read.o"
==> COMPILING "OBJ/i686-linux-gcc/dvd_file.o"
==> COMPILING "OBJ/i686-linux-gcc/dvd_reader.o"
==> COMPILING "OBJ/i686-linux-gcc/walk.o"
==> LINKING "OBJ/i686-linux-gcc/mkisofs"
make[1]: Leaving directory `/root/cdrtools-2.01.01/mkisofs'
==> MAKING "all" ON SUBDIRECTORY "SRCROOT/mkisofs/diag"
make[1]: Entering directory `/root/cdrtools-2.01.01/mkisofs/diag'
==> MAKING "all" ON SUBCOMPONENT "SRCROOT/mkisofs/diag/dump.mk"
make[2]: Entering directory `/root/cdrtools-2.01.01/mkisofs/diag'
==> COMPILING "OBJ/i686-linux-gcc/dump.o"
==> COMPILING "OBJ/i686-linux-gcc/scsi.o"
==> LINKING "OBJ/i686-linux-gcc/devdump"
make[2]: Leaving directory `/root/cdrtools-2.01.01/mkisofs/diag'
==> MAKING "all" ON SUBCOMPONENT "SRCROOT/mkisofs/diag/isodump.mk"
make[2]: Entering directory `/root/cdrtools-2.01.01/mkisofs/diag'
==> COMPILING "OBJ/i686-linux-gcc/isodump.o"
==> LINKING "OBJ/i686-linux-gcc/isodump"

thanks for your help
ttuuxxx

[amigo]

I spent most of yestersay looking around for alternatives to cdrtools. cdrkit is of course okay, but the 'forkers' seem to have lost interest or time to continuew with it. At any rate, cdrkit is basically just an older version of cdrtools before the license terms were changed. BTW, it's the horrid build system which comes under CDDL license. Still the code contains some nasty warnings which are unnecessary.

I found dvdrtools is a fork/patchset which adds features and converts the cdrtools sources to autoconf.

But today I found libburnia (libburn-project.org) which has a tool called cdrskin. The code is completely separate from cdrtools code, but cdrskin emulates most of the syntax as cdrecord -plus additional features are available with the addons libisofs and libisoburn. This seems like it might be a good alternative. The devs are dedicated, the code is all GPL and actively maintained. The install size for libburn/cdrskin is quite small and there are no extra depends. The XFCE goodies program xfburn uses libburn & co.

Perhaps this will allow us all to tell Joerg Schilling to -in the words of Robert Mugabe- "go hang".

[technosaurus]

@ttuuxxx

#!/bin/sh
strip -R .note -R .comment $1

shouldn't this do what you are looking for?

Edit: oops nevermind - didn't refresh my browser before posting...btw I am not liking dillo2

[ttuuxxx]

@ttuuxxx

#!/bin/sh
strip -R .note -R .comment $1

shouldn't this do what you are looking for?

Edit: oops nevermind - didn't refresh my browser before posting...btw I am not liking dillo2

Yes i don't dillo at all its does render properly, It ok for backup, but I'm happy with the seamonkey I compiled for 4.2, its running real nice, not as fast as firepup, but for a series 1.8.1.19 gecko its about as good as it gets. Have you tried 4.2 beta1 yet. we still have a few minor kinks, but it on its way. I just finished compiling xfburn tonight and I really impressed I have it down to a 1.2MB pet for 4.0 series, I'll be releasing it shortly Boy it burns nice. I'm going to try to shrink it a bit more before releasing it.
ttuuxxx

[big_bass]

amigo

But today I found libburnia (libburn-project.org) which has a tool called cdrskin. The code is completely separate from cdrtools code, but cdrskin emulates most of the syntax as cdrecord -plus additional features are available with the addons libisofs and libisoburn. This seems like it might be a good alternative. The devs are dedicated, the code is all GPL and actively maintained. The install size for libburn/cdrskin is quite small and there are no extra depends. The XFCE goodies program xfburn uses libburn & co.

Hey amigo

thanks got it on my slack box easily with these

xfburn-0.3.2-i486-2bb.tgz
libisofs-0.6.12-i486-1as.tgz
libburn-0.5.6-i486-1as.tgz

now for some testing
-----------------------------------
ttuuxxx
great to hear you made a package for puppy
I always burn with K3b when its big
simple stuff I burn with grafburn
puppy needs more choices for burners


great news
Joe