LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Taking good care of my Slackware box ( sysadmin talk ) :-) (https://www.linuxquestions.org/questions/slackware-14/taking-good-care-of-my-slackware-box-sysadmin-talk-765839/)

Alexvader 10-31-2009 01:56 PM

Taking good care of my Slackware box ( sysadmin talk ) :-)
 
Hi Forum

It has been a while since I have started to play with slackware, and now I am getting to like this distro..

It is realy MUCH simpler than the Debians Suses or RHELS... it is just a different paradigm...

Anyway, back to what matters...

There are several packages that I have to compile and install so as to build some apps that do not yet exist as slackBuilds... gsl libraries, GMSH tetrahedral Finite element meshes, OpenCascade, etc...


T think that a much more intelligent approach would be to build a slackware package out from them, and them install/remove them using installpkg/removepkg...

What is the way to do this...?

Make a standard POSIX compliant ./configure-build and then run the checkinstall tool over them, or is there some sort of a standard procedure to do this...?

BRGDS

Alex

disturbed1 10-31-2009 02:25 PM

You should write your own SlackBuild. This is the easiest way to maintain the package across version updates. Gives you a central place to keep build/install notes for that application as well. Plenty of documentation at www.slackbuilds.org, and Alien Bob has a SlackBuild generator. http://alien.slackbook.org/AST/

You can utilize -
make DESTDIR=foo install
cd foo
/sbin/makepkg -l y -c n /tmp/foo-$VERSION-$ARCH-$BUILD.tgz

BrZ 10-31-2009 02:25 PM

A good start point should be Alien's SlackBuild Toolkit.

BrZ 10-31-2009 02:27 PM

lol man, just a few seconds late, look at the post time =]

disturbed1 10-31-2009 02:30 PM

Quote:

Originally Posted by BrZ (Post 3739378)
lol man, just a few seconds late, look at the post time =]

Pinch poke you owe me a coke :)

Alexvader 10-31-2009 02:33 PM

Thkz ppl, for your help

BRGDS

Alex

jedi_sith_fears 10-31-2009 02:59 PM


I just like to add since Slackware 13.0, tgz packages are now made as txz with lzma compression, so follow this convension if you are making slckbuilds of your own. You can also upload them to Slackbuilds.org for helping out other people.

gnashley 10-31-2009 03:16 PM

Let's see, I haven't gotten through all the stuff you mentioned as I have to build cmake-2.6 for gmsh and probably don't have enough room on my box at the moment for OpenCascade, but I know you can get the balling rolling pretty fast with this command:
src2pkg -I ftp://ftp.gnu.org/gnu/gsl/gsl-1.13.tar.gz
And I suspect that this:
src2pkg -I http://geuz.org/gmsh/src/gmsh-2.4.2-source.tgz
The run:
src2pkg -N -Q http://files.opencascade.com/OCC_6.3...ASCADE_src.tgz
src2pkg won't guess the VERSION correctly (how could it in this case), but you can give it with the -N -Q options.
Then run 'src2pkg -X' to execute that build script -provided you have prior depends met.

Alexvader 11-01-2009 11:44 AM

Thx Jedi_sith_fears and Gnashley ( and forum of course... :-) )

As soon as I have some packages ready and working, I think i will just do this and upload them to SlackBuilds (as soon as they could be called stable and working packages )...

My first goals will be Paraview, GMSH, and OpenDX ( OpenCASCADE is needed to help build GMSH with the parasolid format import capability, and since I do a lot of 3d modelling using BRL CAD, and export as Parasolid... it is a sort of a "must"... )

@Gnashley, I am not with my Slackware Box around right now, ( I am using my Deb Lenny at this moment ), so I ask you, is src2pkg a standard tool of Slackware64 13, or must it be downloaded from SBo and installed...?

PS: One more question, how do I know if I can upload any ( working... of course :-) ) packages that I build to SBo...?

For instance can MBDyn from http://www.aero.polimi.it/~mbdyn/ or XFoil and AVL from http://www.aoe.vt.edu/~mason/Mason_f/MRsoft.html or Dakota from http://www.cs.sandia.gov/dakota/, be posted as Slackware Packages, without infringing copyright issues... ?

I ask this because there are lots of interesting software pieces that are not released into public domain through the "standard" sourceforge channel for FLOSS... are they as "Free" as SourceForge ones are...?

BRGDS

Alex


BTW Thx about the src2pkg hint :-)

bgeddy 11-01-2009 12:09 PM

Quote:

PS: One more question, how do I know if I can upload any ( working... of course :-) ) packages that I build to SBo...?
You can't - Slackbuilds doesn't host packages but the Slackbuilds themselves. You can submit a Slackbuild following the guidelines found here.

gnashley 11-01-2009 03:12 PM

Follow the link in my sig to get src2pkg. It comes as an installable noarch package which includes sources for some 'helpers'. After installing run'src2pkg --setup' to build, package and install the helpers. After that you are set to use src2pkf as shown above -you can manually download any sources, of course, instead of doing it with src2pkg.
You mentioned 'checkinstall' -src2pkg comes with 'trackinstall' which replaces checkinstall. checkinstall doesn't work reliably on Slackware since a few versions ago.


All times are GMT -5. The time now is 07:15 AM.