The slack-desc file is the most important thing about your package because if it is not valid, removepkg will not correctly uninstall the package, leaving 'stale' files.

omg really!

Yeah, the slack-desc creator on Linuxpackages.net is your friend. Just make sure you enter in the right data into it and it will create the proper file format.

regards,
...drkstr

Okay thanks again.

I tried doing the 'netsmp' altho I have a package already for it from linuxpackages. I'm just playing now at this part.

But very interesting, when I called the 'make install DESTDIR=/tmp/package-netsmp" it actually installed throughout the system! It didn't install down to my DESTDIR= directory. Do I need to look at a doinst.sh they make in the "make" part of things to verify that the program listens to the argument DESTDIR=SomethingOtherThanDefault?

I hope that makes sense. It's probably just a fluke.

gnashley, not really related to this topic. but i see that you contribute to the amigo project. I have a question for you about it, but it kind of relates to 'packages'

I'm running a few pc's on zipslack so obviously your site caught my eye.

My question is: How would I know with packages that you have available on the amigo site, would require some of OR any of the libraries that are also available there for download.

I'm running a zip-slack 10.2 cut down to almost 68 meg Very lean and mean here.

Developers don't always honor DESTDIR in their makefiles. It really iritates me sometimes. I looked for 'netsmp' on google and really couldn't find anything. Was going to have a look.

If a program doesn't use DESTDIR, it could use one of the following, tho they are rare.

prefix
PREFIX
BUILDROOT

There are a few more that I've run into, just forget them at the moment. Open up the makefile and you might be able to tell what it uses, if anything....

Usually DESTDIR should be used between make and install like this:
make DESTDIR=/your/path install

This is even more reliable:
make DESTDIR=/your/path --prefix=/usr/bin install

OLD_FOGIE, I *am* Amigo Linux. About my site:

I concentrate on GTK-1.2 apps that should only need GTK, GLIB, gdk-pixbuf and lesstif. Mostly these are in Applications or GuiComponents.

Xapps -stuff in there should run with just X and maybe xaw3d.
Extra -contains stuff you don't want like GTK2 and GNOME apps.

Utils has some mostly CLI or 'background' utilities.

Most applications which need anything unusual will have a README or other note in there to tell you -be sure to always look in the Resources directory if there is one. I try to include any tips you might need -for instance there are sources there which can only be compiled with an older compiler,etc.

The Libs directory should have any extra libraries which are not part of Slackware official which are needed by any application from the site. There are also some unusual and legacy libraries there which may not be needed by any of the programs I distribute.

I always do a "find in files" for "destdir" before building any package with this option. SOme times it it supported in the make file, configure file or both. So if the search finds a match in any of these files, you should be good to go. If not, you need to open them up and find out how the developer wants you to acomplish this. As said before, very annoying.

regards,
...drkstr

Yes, that is the challenge when trying to build a package - never expect the "make install DESTDIR=..." to work all the time. Logging the actions of the "make install" and carefully going through that log will help you find files that got installed across your own filesystem nevertheless. I use installwatch (part of checkinstall nowadays) to do that logging for me since it is more easily readable.

Eric

I had downloaded the 'source' from the project page at sourceforge's web-site. The project page is: http://sourceforge.net/project/showf...group_id=12694

It is used to connect to an HP Officejet Printer.

Thanks gnashley for the further explanation on the Amigo project. If I know myself, I'm sure I will have more tho hahah LOL

I had to chuckle when I was installing zip-slack for the first time at this paragraph from here:

http://slackware.com/faq/do_faq.php?faq=zipslack#1

The thought of me being a sysadmin really frightens me lol.

Running a light desktop at first was akward, but I'm really getting the hang of using blackbox. Once I learned how to customize the right click menu it got much easier. It's amazing, you can actually do work on a pc w/out desktop icons or a fancy taskbar. I'm under 480 meg on one pc and it just flies. I still think zip slack is very under-rated/embraced by the community

Thanks jong for the heads up on other DESTDIR examples, I wrote them down in my linux notebook over here. Yes a paper book for a computer.

Eric's always light years ahead of me So let me see if I get this straight, you run in a virtual linux to make packages, and have an install watch too. I thought I was high tech w/a coffee pot that turned on in the morning.

Bye for now.

Fogie

But I do have a package for net-snmp here:
http://www.slackware.com/~alien/slac...et-snmp/build/
Or at least, the SlackBuild and other stuff to build it for your 10.2 release. The binary package I have stored up there is "only" for Slackware 10.0 and since my build box is down due to bad RAM, I can not quickly rebuild it for Slackware-10.2.

Eric

If your shopping for value ram I find the centon's work pretty good. They usually have some play in the clock frequencies.

Bye for now.

I run a 2.6.16.14 kernel with udev, but I am using PiterPUNK's version at http://piterpunk.info02.com.br/extra/ but with some additional network tweaks that Piter is going to add to his next release.
I have 2 wired and two wireless NICs in this desktop and they all work with this combination (both wireless are on WPA, one using madwifi and the other using rt2500).
If Piter is slow making an updated package I can post what I did to get the networking working flawlessly.

Eric

Hi Eric,

you know in madwifi for wpa where you:

CONFIG_DRIVER_MADWIFI=y
CFLAGS += -I/path/to/madwifi-ng
CONFIG_CTRL_IFACE=y

well I deleted my madwifi-ng sources as I made a package LOL. can wpa supplicant still be put in?

If you made a madwifi package using my SlackBuild and installed it, then wpa_supplicant does not need the madwifi sources. The madwifi package will have installed everything that wpa_supplicant.SlackBuild needs to add support for the madwifi driver.
And be sure to use my latest wpa_supplicant.SlackBuild ... it is better laid out and will even build a package when no madwifi files are found (but then of course it will not have madwifi support)... nice for all the people without madwifi cards for whom the SlackBuild would fail to build previously :-) It also contains man pages for the wpa_supplicant, wpa_cli and wpa_supplicant.conf .... plus the wpa_gui (forgot to add a .desktop file so it will not sow up in any Window Manager menu... that is something on the TODO list for my next build).

Eric