LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-09-2011, 03:36 PM   #1
madsovenielsen
Member
 
Registered: Aug 2009
Posts: 183

Rep: Reputation: 15
Making Slackware 13.1 packages


Hello

http://altctrlbackspace.blogspot.com...om-source.html

I have followed this guide and have made some packages on a system running Slack 12.2 - Everything is fine.

But it's not working on Slack 13.1

I get no error messages. But when i try to install the finished package with pkgtool it takes about 2 seconds to finish and nothing is installed.

I know that the method from the guide works, at least on 12.2 - Why does this not work on 13.1 ?
 
Old 08-09-2011, 03:47 PM   #2
madsovenielsen
Member
 
Registered: Aug 2009
Posts: 183

Original Poster
Rep: Reputation: 15
Correction:

It seems to work for some packages.

I have made a Python 2.7.2 package, nothing wrong with it, works fine.

But it doesn't seem to work with Apache httpd 2.2.19 both on Slack 12.2 and 13.1

Why ?

Update:

Following this guide also result in a uninstallable httpd package

http://slackwiki.org/Building_A_Package

Again, no error messages during the build process or install

Last edited by madsovenielsen; 08-09-2011 at 04:21 PM.
 
Old 08-09-2011, 05:00 PM   #3
Mike_M
Member
 
Registered: Mar 2011
Location: California
Distribution: Slackware
Posts: 116

Rep: Reputation: 53
Without more information it is going to be pretty difficult for anyone to help you troubleshoot. "It doesn't work" is not a very complete error report. What are the contents of these packages you are creating? Slackware packages are compressed tar files, so looking at the contents is easy enough to do. How are you verifying nothing is being installed? Also, some software requires special handling. Simple online instructions for creating a package may not work in all cases.

Is there some reason you aren't using the httpd-2.2.19 package that is already part of Slackware 13.1? If you want to customize the build in some way you could download the source directory for httpd from your favorite Slackware mirror, change the configuration options, and rebuild.
 
Old 08-09-2011, 05:19 PM   #4
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,836
Blog Entries: 1

Rep: Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251
Mike is right, you really shouldn't replace stock slackware packages unless you've got a good reason. If you do, just modify the slackbuilds from the slackware official mirrors.

Additionally, the steps mentioned in that tutorial will not work for all packages. You should always read the installation instructions of a particular package.
 
Old 08-10-2011, 02:43 AM   #5
madsovenielsen
Member
 
Registered: Aug 2009
Posts: 183

Original Poster
Rep: Reputation: 15
The Apache httpd package supplied with 13.1 is 2.2.15

I can't post the content of the package here because it exceeds the limit of 30000 chars.

But it seems to be okay.
 
Old 08-10-2011, 02:53 AM   #6
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,836
Blog Entries: 1

Rep: Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251
Quote:
Originally Posted by madsovenielsen View Post
The Apache httpd package supplied with 13.1 is 2.2.15

I can't post the content of the package here because it exceeds the limit of 30000 chars.

But it seems to be okay.
2.2.19 can be found in 13.1 patches directory:
http://www.mirrorservice.org/sites/f...ches/packages/
 
Old 08-10-2011, 02:54 AM   #7
Mike_M
Member
 
Registered: Mar 2011
Location: California
Distribution: Slackware
Posts: 116

Rep: Reputation: 53
Quote:
Originally Posted by madsovenielsen View Post
The Apache httpd package supplied with 13.1 is 2.2.15
That is what initially shipped with Slackware 13.1 when it was released. It has since been upgraded to 2.2.19. Look in the patches/ directory of your favorite Slackware mirror for either the binary package or the source.

If you aren't already, you may want to subscribe to the slackware-security mailing list so that you are made aware of these security updates, including the download URL to update itself. If you're still running Apache httpd 2.2.15 on a Slackware 13.1 machine, you missed out on four security notifications and updates.
 
Old 08-10-2011, 04:14 AM   #8
madsovenielsen
Member
 
Registered: Aug 2009
Posts: 183

Original Poster
Rep: Reputation: 15
Ahh! okay. Thanks a lot

But i really still want to learn how to make packages for slackware.
 
Old 08-10-2011, 04:20 AM   #9
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,836
Blog Entries: 1

Rep: Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251
Quote:
Originally Posted by madsovenielsen View Post
Ahh! okay. Thanks a lot

But i really still want to learn how to make packages for slackware.
You might want to have a look at the slackbuilds writing tutorial. That's a recommended way of creating slackware packages.
http://www.slackwiki.org/Writing_A_SlackBuild_Script

Have fun.

edit: also have a look at the structure of other slackbuilds on www.slackbuilds.org. It'll give you a better idea of slackbuilds.

Last edited by sycamorex; 08-10-2011 at 04:22 AM.
 
Old 08-10-2011, 09:14 AM   #10
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,200

Rep: Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307
Quote:
Originally Posted by madsovenielsen View Post
But i really still want to learn how to make packages for slackware.
In the cases of Apache and Python, the sources for building the packages are available on any Slackware mirror. You just download the slackware(64)-$VERSION/source/whatever directory. In that directory, you'll find a file whose extension is .SlackBuild. Run that .SlackBuild, and the package will be built. If you want to change things, then just edit the SlackBuild file.
 
Old 08-10-2011, 02:00 PM   #11
madsovenielsen
Member
 
Registered: Aug 2009
Posts: 183

Original Poster
Rep: Reputation: 15
Great. I will do that.

Thanks
 
Old 08-10-2011, 04:02 PM   #12
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Rep: Reputation: 232Reputation: 232Reputation: 232
Looking at the link you supplied it recommends changing to the build directory pkg and running makepkg pkgname which worked in Slackware-12.2 but will not work in Slackware-13.1 giving you "ERROR: Can't make output package in current directory.". I'm not sure why you are not seeing this error reported from makepkg.

You now have to build a package outside of the directory you are building a package in - which make sense. So makepkg ../pkgname will work but not makepkg pkgname whilst in the pkg directory in which you have built the package.

Credit for wanting to build then install packages rather than the simple configure,make,make install source building as package management makes your system far more maintainable and robust.

As others have suggested I highly recommend looking at Slackbuild scripts, after all Slackware itself was built this way, and figuring out how they work. The source directory on the Slackware repos have Slackbuild scripts showing how the components of the distro were built - very educational.
 
Old 08-11-2011, 05:41 AM   #13
madsovenielsen
Member
 
Registered: Aug 2009
Posts: 183

Original Poster
Rep: Reputation: 15
Quote:
Credit for wanting to build then install packages rather than the simple configure,make,make install source building as package management makes your system far more maintainable and robust.
Thanks.

Thats excactly why i want to know how to make packages.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] How can I search for unofficial packages in Slackware? *Packages like guake terminal* theif519 Slackware 7 06-24-2011 06:30 PM
[SOLVED] Making your own packages in Arch Mr. Alex Arch 2 12-27-2010 08:11 AM
Making Slackware Packages 202 Old_Fogie Slackware 3 11-17-2006 02:02 AM
Making slackware packages - What Magic To Use? Old_Fogie Slackware 34 06-03-2006 09:07 PM
Making Slackware Packages tjm Slackware 5 07-31-2003 11:46 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:57 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration