Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
11-09-2014, 05:42 PM
|
#1
|
Member
Registered: May 2010
Posts: 621
Rep: 
|
How to replace the official slackpkg repo?
I am looking for a good way to replace the official slackpkg repo. The goal is to have my own private repo which is similar, but not identical to the official repo, and is accessible via slackpkg just as the official repo would be. I think I am basically on the right track, but I'd like any pointers you can offer. Here's what I did so far:
I copied the basic folder hierarchy found below http://mirrors.kernel.org/slackware/slackware64-14.1/. I didn't copy everything, but just populated it with folders slackpkg expects to find. I used Alien's gen_repos_files.sh  to generate the lists, using my own signing key. I had to run it several times: once for the repo root and once for each subfolder (slackware64, patches, etc.). Then I changed the slackpkg mirror.
I found that slackpkg checks signatures against ANY key on root's keyring, so as soon as I added my key there, my signatures were accepted. I am assuming I could have a repo where some packages are signed by, say, PV, and others by me, all without modifying slackpkg. [Edit: don't listen to me. /etc/slackpkg/slackpkg.conf has a SLACKKEY variable, which seems to be the right way to change the repo signing key.] My sandbox had only a single file, and things seemed to work (I tried search, update, and upgrade-all).
What I basically want now is to compare this approach to what others have done, and hopefully learn a better way to do it. Note that I have little interest in using other packagers at this moment (like slackpkg+), since my goal is very specific: replacing the main repo.
Last edited by qweasd; 11-13-2014 at 03:37 PM.
|
|
|
11-10-2014, 01:12 AM
|
#2
|
Senior Member
Registered: Feb 2009
Posts: 1,727
|
you can use slackpkg+ and set priorities on repos, so no need to replace everything
there are several tutorials/howtows on how to add a own repo to the list or repos,
I think microlinux is a good starting point to search for information on how ot do this
|
|
|
11-10-2014, 05:07 AM
|
#3
|
Member
Registered: Jun 2009
Distribution: Slackware
Posts: 190
Rep: 
|
Friendly manuals
grep file /etc/slackpkg/mirrors
Quote:
# You can include new mirrors in this file. Many people have mirrors
# file://path/to/some/directory/
|
man slackpkg.conf
Quote:
PRIORITY
This array selects the priority at which directories on the mirror
will have when slackpkg looks for packages. If a package is found
in more than one place, the package in first directory gets prior-
ity, then second, then third, then fourth and finally, the package
found in last listed directory. You can use %PKGMAIN to use the
contents of PKGMAIN variable.
Default values (in order): patches %PKGMAIN extra pasture testing
|
HTH
Last edited by EYo; 11-10-2014 at 05:08 AM.
Reason: spelling correction
|
|
|
11-10-2014, 05:13 AM
|
#4
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559
|
Quote:
Originally Posted by qweasd
I used Alien's gen_repos_files.sh  to generate the lists, using my own signing key. I had to run it several times: once for the repo root and once for each subfolder (slackware64, patches, etc.)
|
Check out the script's "REPO_SUBDIRS" variable. You only have to run the script once if you define that variable properly.
Eric
|
|
|
11-10-2014, 11:27 AM
|
#5
|
MLED Founder
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453
|
I'm using the official repos as well as a series of third-party repos for my MLED project. Here's some basic documentation to get you started, even if you don't use it later on:
http://www.microlinux.fr/mled_installation.php
|
|
|
11-12-2014, 04:21 PM
|
#6
|
Member
Registered: May 2010
Posts: 621
Original Poster
Rep: 
|
Thanks everyone! I have another related question.
What is the deal with maketag, maketag.ez (why the same?) [Edit: hardlinked], and tagfile? The best I can tell they have something to do with setup. Am I right to assume that slackpkg ignores them completely?
Last edited by qweasd; 11-13-2014 at 03:36 PM.
|
|
|
11-12-2014, 04:39 PM
|
#7
|
MLED Founder
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453
|
Tagfiles are useful if (like me) you sometimes have to deal with something like dozens of identical installations. They're like a bone-headed version of Red Hat's kickstart files. If you have a precise idea of what you have to deploy, you can edit a set of tagfiles and then use them during the installation. Watch out for the "tagfiles" selection dialog next time you install Slackware.
Daniel de Kok explains tagfiles in detail in his Slack Basics book.
http://rlworkman.net/howtos/slackbasics.pdf
|
|
|
11-12-2014, 04:44 PM
|
#8
|
Member
Registered: May 2010
Posts: 621
Original Poster
Rep: 
|
Thanks kiki!
|
|
|
11-12-2014, 07:10 PM
|
#9
|
Member
Registered: May 2010
Posts: 621
Original Poster
Rep: 
|
Is there something like a scripty that generates maketag from tagfile? It actually looks like PV may be editing each maketag by hand...
|
|
|
11-13-2014, 06:32 AM
|
#10
|
MLED Founder
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453
|
Quote:
Originally Posted by qweasd
Is there something like a scripty that generates maketag from tagfile? It actually looks like PV may be editing each maketag by hand...
|
I only use this script to extract the tagfiles from a Slackware DVD:
http://www.microlinux.fr/slackware/t...py-tagfiles.sh
The rest is rather something in the line of :1,$s/REC/ADD/g in Vim.
|
|
1 members found this post helpful.
|
11-13-2014, 02:28 PM
|
#11
|
Member
Registered: May 2010
Posts: 621
Original Poster
Rep: 
|
Wow, this excursion really taught me quite a bit about Slackware. When I started, I couldn't hope that things will turn out so magically KISS, yet scalable and robust. The installer, for example, that gets so much flak in "reviews", is a perfect example of a robust tool handcrafted to perfection. I am very impressed. 
|
|
|
All times are GMT -5. The time now is 10:54 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|