-
Notifications
You must be signed in to change notification settings - Fork 8
/
Copy pathFAQ.html
1288 lines (942 loc) · 52.4 KB
/
FAQ.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" -->
<html>
<head>
<title>FAQ</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css">
a{
text-decoration:none;
}
</style>
</head>
<body font="Verdana">
<b><h1>Frequently Asked Questions:</h1></b>
<pre>
*Contents
<a href="FAQ.html#slgFAQ1">1. What is slapt-get ?</a>
<a href="#slgFAQ2">2. Why yet another package management tool for Slackware?</a>
<a href="#slgFAQ3">3. How do I build/install slapt-get? How do I remove slapt-get?</a>
<a href="#slgFAQ4">4. How do I find a package I want to install?</a>
<a href="#slgFAQ5">5. Can I upgrade all my installed packages?</a>
<a href="#slgFAQ6">6. How can I see what will be upgraded without upgrading?</a>
<a href="#slgFAQ7">7. What if I only want to download the updates?</a>
<a href="#slgFAQ8">8. How can I re-install an existing package?</a>
<a href="#slgFAQ9">9. Can I "dist-upgrade" to a newer Slackware release?</a>
<a href="#slgFAQ10">10. What about package dependencies?</a>
<a href="#slgFAQ11">11. What about multiple package sources, ala linuxpackages.net?</a>
<a href="#slgFAQ12">12. How can I get more detailed statistics for downloads?</a>
<a href="#slgFAQ13">13. How can I install every available package?</a>
<a href="#slgFAQ14">14. What if I only want to upgrade one package?</a>
<a href="#slgFAQ15">15. What about Dropline support?</a>
<a href="#slgFAQ16">16. How can I generate an exclude list for an entire disk set?</a>
<a href="#slgFAQ17">17. How do I create my own package source?</a>
<a href="#slgFAQ18">18. How can I download every package in a disk set?</a>
<a href="#slgFAQ19">19. How can I add dependency information to my packages?</a>
<a href="#slgFAQ20">20. How do I get the newest development version of slapt-get?</a>
<a href="#slgFAQ21">21. How can I contribute my ideas or code?</a>
<a href="#slgFAQ22">22. How can I get slapt-get to speak in my native tongue?</a>
<a href="#slgFAQ23">23. How do I set the output language?</a>
<a href="#slgFAQ24">24. How do I specify proxy settings?</a>
<a href="#slgFAQ25">25. How can I exclude all *pre*, *beta*, and *686* packages safely?</a>
<a href="#slgFAQ26">26. How does the transaction engine work?</a>
<a href="#slgFAQ27">27. How does the package version comparison algorithm work?</a>
<a href="#slgFAQ28">28. I am tracking current, how do I keep the base disk set up to date?</a>
<a href="#slgFAQ29">29. How would I script an ldd dependency hack with slapt-get?</a>
<a href="#slgFAQ30">30. Does EXCLUDE work for install as well as upgrade and dist-upgrade?</a>
<a href="#slgFAQ31">31. What about package conflicts? How can I specify a conflict for my package?</a>
<a href="#slgFAQ32">32. Is the ROOT environment variable honored for install and upgrading?</a>
<a href="#slgFAQ33">33. How do I specify the exact version of a package to install?</a>
<a href="#slgFAQ34">34. Why is upgradepkg complaining it cannot find installpkg or removepkg, with sudo?</a>
<a href="#slgFAQ35">35. How can I specify a username/password for the connection to the package source?</a>
<a href="#slgFAQ36">36. /var/slapt-get is growing large, how can I safely free up space?</a>
<a href="#slgFAQ37">37. What about extra, testing, or pasture packages?</a>
<a href="#slgFAQ38">38. Can I use slapt-get to mirror packages?</a>
<a href="#slgFAQ39">39. Is there a way to use tab completion for the package names in Bash?</a>
<a href="#slgFAQ40">40. How do I remove obsoleted packages?</a>
<a href="#slgFAQ41">41. What provisions have you made for dialup users?</a>
<a href="#slgFAQ42">42. Is there a way to get a report with the pending updates emailed to me?</a>
<a href="#slgFAQ43">43. What if I don't trust third party sources for upgrades?</a>
<a href="#slgFAQ44">44. How do I specify an addon that is not a dependency of my package?</a>
<a href="#slgFAQ45">45. Will slapt-get break my system?</a>
<a href="#slgFAQ46">46. What is a meta package and how can I take advantage of it?</a>
<a href="#slgFAQ47">47. How can I downgrade a package?</a>
<a href="#slgFAQ48">48. How can I search the contents of a package for a file or library?</a>
<a href="#slgFAQ49">49. Will slapt-get support a --compile like option for slackbuilds?</a>
<a href="#slgFAQ50">50. What about mirror fall back / fail-over ?</a>
<a href="#slgFAQ51">51. How do I install a kernel rather than upgrade the existing kernel?</a>
<a href="#slgFAQ52">52. What are the relationships of CHECKSUMS.md5, PACKAGES.TXT and package_data?</a>
<a href="#slgFAQ53">53. Does slapt-get support the GPG/PGP signature verification?</a>
<a href="#slgFAQ54">54. Why am I getting "GPGME: Invalid crypto engine"?</a>
<a href="#slgFAQ55">55. How do I support GPG signature verification in my package repository?</a>
<a href="#slgFAQ56">56. What does "GPGME: Bad file descriptor, GPG key could not be imported." mean?</a>
<a href="#slgFAQ57">57. How do I assign priorities to my package sources?</a>
<a name="slgFAQ1"><b>1. What is slapt-get ?</b></a>
slapt-get is an APT like system for Slackware package management. It allows
one to search slackware.com and mirrors for packages, compare them with
installed packages, install new packages or upgrade installed packages all
with a few simple commands. Great for scripting as well.
slapt-get is not affiliated or endorsed by Patrick Volkerding / slackware.com.
<a name="slgFAQ2"><b>2. Why yet another package management tool for Slackware?</b></a>
Various reasons came together which inspired me to create slapt-get. I was
trying to explain to a good friend of mine the functionality provided by
apt-get on Debian GNU/Linux. And I needed a uniform and easily scripted
method of installing software on various User-Mode Linux instances I was
using for development. Thus slapt-get was born.
<a name="slgFAQ3"><b>3. How do I build/install slapt-get? How do I remove slapt-get?</b></a>
Two ways to install:
A: You can build slapt-get from source and use the 'install' make target,
B: You can build from source and make a Slackware package with the 'pkg'
make target. Then install the generated package within the newly created
'pkg' directory.
If you installed via `make install`, there is an 'uninstall' make target.
If you installed the slack package, then use removepkg.
See the INSTALL file included with slapt-get.
<a name="slgFAQ4"><b>4. How do I find a package I want to install?</b></a>
You can use the --search feature, supplying an expression. POSIX
and extended regular expressions are supported. This searches the name,
version, location, or description of packages.
<a name="slgFAQ5"><b>5. Can I upgrade all my installed packages?</b></a>
Yes, use the --upgrade option. slapt-get will check for newer versions of all
packages already installed.
Please review the Slackware ChangeLog.txt for the Slackware release you are
running. This is especially important for -current.
<a name="slgFAQ6"><b>6. How can I see what will be upgraded without upgrading?</b></a>
If the transaction report is not enough, use the --simulate option before
--upgrade. See slapt-get --help
<a name="slgFAQ7"><b>7. What if I only want to download the updates?</b></a>
Use the --download-only option with --upgrade.
See slapt-get --help
<a name="slgFAQ8"><b>8. How can I re-install an existing package?</b></a>
Use the --reinstall option with --install pkg_name.
See slapt-get --help
<a name="slgFAQ9"><b>9. Can I "dist-upgrade" to a newer Slackware release?</b></a>
Yes. See also <a href="http://slackwiki.org/Upgrade_Using_Slapt-get">http://slackwiki.org/Upgrade_Using_Slapt-get</a>.
Change your source location within /etc/slapt-get/slapt-getrc to point to
the newer release directory. --update your local package cache, then
--dist-upgrade to the newer release. You will also want to disable any
third party package sources while upgrading to a newer release due to the fact
that third party packages might not be as rigorously tested as official
packages, or may cause conflicts with files provided by official packages.
For instance, you have the following line as your source:
SOURCE=ftp://distro.ibiblio.org/pub/Linux/distributions/slackware/slackware-9.0/
Simply change the URL to point to current, like so:
SOURCE=ftp://distro.ibiblio.org/pub/Linux/distributions/slackware/slackware-current/
CAVEAT: Follow the instructions in UPGRADE.TXT.
Now you --dist-upgrade to retrieve the package data for that release.
What dist-upgrade does is basically make sure that any missing packages
from the base disk set are installed, as well as upgrade to any newer
versions of the currently installed packages. All of this happens in
one transaction.
dist-upgrade'ing involves doing the following:
### upgrade your local package cache
$ slapt-get --update
### first, download all of the packages prior to upgrading
$ slapt-get --dist-upgrade --download-only
### second, install (not upgrade!) the newest kernel
$ slapt-get --install kernel --no-upgrade
### then, upgrade the most important
#(this installs any newer versions)
$ slapt-get --install glibc-solibs pkgtools sed
In newer versions of slapt-get, dist-upgrade automatically handles
installing/upgrading glibc-solibs, pkgtools, and sed prior to any
other changes.
### finally, let slapt-get upgrade the rest
$ slapt-get --dist-upgrade
You can specify --remove-obsolete to remove all depreciated packages.
CAUTION: this can only take into consideration packages that are available
from your current sources. Thus self made packages will be considered
obsolete as well (they can be excluded within slapt-getrc, however). Only
use this if you have been using Slackware packages exclusively. You can
also use this option for information purposes, observing the obsolete
packages, then passing all the ones you are sure of to --remove (which can
accept multiple packages at once).
### dist upgrade and remove all depreciated/obsolete packages
$ slapt-get --dist-upgrade --remove-obsolete
Then follow the rest of the directions in UPGRADE.TXT.
You should make sure any new packages within the disk sets you are using are
also installed, as they will not be detected during --dist-upgrade, as only
packages already installed will be upgraded. To accomplish this, you can
specify slapt-get to install a disk set like so:
### install all X and X application packages
$ slapt-get --install-set x xap
Do the same for all your installed disk sets, such as gnome, x, xap, l, n, etc.
Piotr Simon has a script that easily identifies new packages from release
release. You can find it here:
<a href="http://www.tenboard.com/slackware/index.php?path=SlackBuilds/">http://www.tenboard.com/slackware/index.php?path=SlackBuilds/</a>
<a name="slgFAQ10"><b>10. What about package dependencies?</b></a>
First of all, slapt-get does not provide dependency resolution for vanilla
Slackware packages (ie, official Slackware packages that come with the
distribution).
However, slapt-get does provide a framework for dependency resolution for
packages that follow the Slackware package format, while still being backwards
compatible. This information is stored in so called meta files within the
package. slapt-get does not parse the packages themselves. It uses the
PACKAGES.TXT package database that Patrick Volkerding provides along with his
packages. slapt-get uses this file by extending it with optional extra fields.
This information is stored within the package simply as a means of easy
transport, to later be parsed into a PACKAGES.TXT. For example, the entry
for man within PACKAGES.TXT looks like:
PACKAGE NAME: man-1.5l-i386-1.tgz
PACKAGE LOCATION: ./slackware/ap
PACKAGE SIZE (compressed): 166 K
PACKAGE SIZE (uncompressed): 390 K
PACKAGE DESCRIPTION:
man: man (format and display the on-line manual pages)
It is extended like so:
PACKAGE NAME: man-1.5l-i386-1.tgz
PACKAGE MIRROR: http://www.slackware.at/data/slackware-9.1/
PACKAGE LOCATION: ./slackware/ap
PACKAGE SIZE (compressed): 166 K
PACKAGE SIZE (uncompressed): 390 K
PACKAGE REQUIRES: groff >= 1.56-noarch-1,man-pages | man-pages-de
PACKAGE CONFLICTS:
PACKAGE SUGGESTS:
PACKAGE DESCRIPTION:
man: man (format and display the on-line manual pages)
The REQUIRES line is an addition supported by slapt-get, along with CONFLICTS
and SUGGESTS. The meta files supporting dependencies, conflicts, and
suggestions are within the packages inside the ./install/ directory. The
REQUIRES information is stored in the slack-required file. The CONFLICTS
information is stored within the slack-conflicts file. The SUGGESTS
information is stored in the slack-suggests file. See <a href="#slgFAQ19">FAQ #19</a> for a breakdown
of the structure of REQUIRES, <a href="#slgFAQ31">FAQ #31</a> for CONFLICTS, and <a href="#slgFAQ44">FAQ #44</a> for SUGGESTS.
MIRROR is an optional location so that the packages can be hosted elsewhere
(this is the internal representation slapt-get uses after caching the package
date from the remote package source).
This information is added to the PACKAGES.TXT file by extracting it from the
meta files within the package. This is normally done by the provider of the
packages when they generate the PACKAGES.TXT support file for their package
source. See <a href="#slgFAQ17">FAQ #17</a> for an example script to generate an extended PACKAGES.TXT
file.
The inclusion of this information within the Slackware package format does not
inhibit the ability for Slackware pkgtools to install these packages. This
information is silently ignored and discarded after the package is installed.
Packages supporting this framework can be found at linuxpackages.net, along
with several Slackware derived distributions such as CollegeLinux (starting
with 2.5) and VectorLinux (starting with 5.0).
Also, Stefano Stabellini has created a PACKAGES.TXT that contains the
dependency information for Slackware packages without modifying the actual
packages themselves. This can be used as a slapt-get source to pull the
packages from official slackware.com mirrors. Read more about it at
Stefano's page: <a href="http://www.stabellini.net/depslack.html">http://www.stabellini.net/depslack.html</a>
<a name="slgFAQ11"><b>11. What about multiple package sources, ala linuxpackages.net?</b></a>
You can use multiple sources with slapt-get (including linuxpackages.net).
See the example slapt-getrc in the source tarball or look in the
slapt-get directory within /usr/doc/ if you installed a binary package.
See the README for further details.
<a name="slgFAQ12"><b>12. How can I get more detailed statistics for downloads?</b></a>
If you would like more notification on downloading pkgs/files, use the
command line option --show-stats (or -S). This will show curl style
download information.
<a name="slgFAQ13"><b>13. How can I install every available package?</b></a>
Even though it is not built in, it is simple since slapt-get is easy to script
with. Here is how to install every package that is available but not
currently installed:
slapt-get --available|grep inst=no|awk '{print $1}'|uniq|xargs -r slapt-get --install
<a name="slgFAQ14"><b>14. What if I only want to upgrade one package?</b></a>
The --install option works for this as well. If the package is already
installed, it will check and install any newer versions:
slapt-get --install {pkg_name}
<a name="slgFAQ15"><b>15. What about Dropline support?</b></a>
There is no direct support for Dropline packages. If you do not want them
upgraded, put either the package names or a regex into the exception list.
Use the following to exclude Dropline (from the example slapt-getrc):
EXCLUDE=kernel-ide,kernel-source,kernel-headers,kernel-modules,lilo,.*-[0-9]+dl$,devs
<a name="slgFAQ16"><b>16. How can I generate an exclude list for an entire disk set?</b></a>
You can exclude an entire disk set by placing the disk set as an exclude. Be
sure to use the beginning-of-line (^) and end-of-line ($) operators for
specific matching. For example:
To exclude all of ./slackware/x and ./slackware/xap
EXCLUDE=^./slackware/x$,^./slackware/xap$
<a name="slgFAQ17"><b>17. How do I create my own package source?</b></a>
Within slapt-getrc, change your SOURCE= lines to point to your package
source. This might be a local source using file:// URLs, or a publicly
available source.
For example, you could have an official and a local source like:
SOURCE=ftp://ftp.slackware.no/pub/linux/slackware/slackware-9.1/
SOURCE=file:///usr/src/local_pkg_repository/
This local directory must have the PACKAGES.TXT and CHECKSUMS.md5 files
present. This could be a mounted Slackware release CDROM, or a custom
repository.
The CHECKSUMS.md5 file can be generated with find:
rm CHECKSUMS.md5; find . -name '*.tgz' -exec md5sum {} >> CHECKSUMS.MD5 \;
The PACKAGES.TXT can be generated by the following script:
### BEGIN SCRIPT
#!/bin/sh
#DL_URL=http://your_remove_pkg_host.tld/packages/
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# any later version.
function gen_packages_txt {
echo '' > PACKAGES.TXT
find . -type f -name '*.meta' -exec cat {} \; >> PACKAGES.TXT
cat PACKAGES.TXT | gzip -9 -c - > PACKAGES.TXT.gz
}
function gen_md5_checksums {
echo '' > CHECKSUMS.md5
find . -type f -regextype posix-egrep -regex '.*\.[tgblzikx]+$' -exec md5sum {} \; >> CHECKSUMS.md5
cat CHECKSUMS.md5 | gzip -9 -c - > CHECKSUMS.md5.gz
}
function gen_meta {
if [ ! -f $1 ]; then
echo "File not found: $1"
exit 1;
fi
if [ "`echo $1|grep -E '(.*{1,})\-(.*[\.\-].*[\.\-].*).[tgblzikx]{2,}[ ]{0,}$'`" == "" ]; then
return;
fi
PKGEXT=${1##*.}
case $PKGEXT in
tgz) DECOMPRESS=gzip ;;
tbz) DECOMPRESS=bzip2 ;;
tlz) DECOMPRESS=lzma ;;
txz) DECOMPRESS=xz ;;
esac
NAME=$(echo $1|sed -re "s/(.*\/)(.*.$PKGEXT)$/\2/")
LOCATION=$(echo $1|sed -re "s/(.*)\/(.*.$PKGEXT)$/\1/")
SIZE=$(du -bk $1 | awk '{print $1}')
USIZE=$(expr $(cat $1 | $DECOMPRESS -dc | wc -c) / 1024)
REQUIRED=$($DECOMPRESS -dc $1 | tar -xO install/slack-required 2>/dev/null|xargs -r -iZ echo -n "Z,"|sed -e "s/,$//")
CONFLICTS=$($DECOMPRESS -dc $1 | tar -xO install/slack-conflicts 2>/dev/null|xargs -r -iZ echo -n "Z,"|sed -e "s/,$//")
SUGGESTS=$($DECOMPRESS -dc $1 | tar -xO install/slack-suggests 2>/dev/null|xargs -r )
METAFILE=${NAME%$PKGEXT}meta
echo "PACKAGE NAME: $NAME" > $LOCATION/$METAFILE
if [ -n "$DL_URL" ]; then
echo "PACKAGE MIRROR: $DL_URL" >> $LOCATION/$METAFILE
fi
echo "PACKAGE LOCATION: $LOCATION" >> $LOCATION/$METAFILE
echo "PACKAGE SIZE (compressed): $SIZE K" >> $LOCATION/$METAFILE
echo "PACKAGE SIZE (uncompressed): $USIZE K" >> $LOCATION/$METAFILE
echo "PACKAGE REQUIRED: $REQUIRED" >> $LOCATION/$METAFILE
echo "PACKAGE CONFLICTS: $CONFLICTS" >> $LOCATION/$METAFILE
echo "PACKAGE SUGGESTS: $SUGGESTS" >> $LOCATION/$METAFILE
echo "PACKAGE DESCRIPTION:" >> $LOCATION/$METAFILE
$DECOMPRESS -dc $1 | tar -xO install/slack-desc |grep -E '\w+\:'|grep -v '^#' >> $LOCATION/$METAFILE
echo "" >> $LOCATION/$METAFILE
}
case "$1" in
pkg)
if [ -n "$2" ]; then
gen_meta $2
else
echo "$0 [pkg [file]|all|new|PACKAGESTXT|MD5]"
fi
;;
all)
for pkg in `find . -type f -regex '.*\.[tgblzikx]+$' -print`
do
gen_meta $pkg
done
$0 PACKAGESTXT
$0 MD5
;;
new)
for pkg in `find . -type f -regex '.*\.[tgblzikx]+$' -print`
do
if [ ! -f ${pkg%${pkg##*.}}meta ]; then
gen_meta $pkg
fi
done
;;
PACKAGESTXT)
gen_packages_txt
;;
MD5)
gen_md5_checksums
;;
*)
echo "$0 [pkg [file]|all|new|PACKAGESTXT|MD5]"
;;
esac
### END SCRIPT
<a name="slgFAQ18"><b>18. How can I download every package in a disk set?</b></a>
You can use the install-set option to install all of the packages within a
disk set.
To install every package from xap:
slapt-get --install-set xap
Disk set names are not hardcoded. slapt-get performs a search for any
packages with a location of /{disk_set_arg}$. So custom repositories
with directory structures of ./foo, ./bar, and ./baz can use "foo", "bar", and
"baz" as --install-set options.
<a name="slgFAQ19"><b>19. How can I add dependency information to my packages?</b></a>
This is for package developers. If you are not a package developer, please
request your packager include this information.
To export the dependency data for a package, include within your package the
following file:
./install/slack-required
The structure of this file is one entry per line in the following format:
package_name
or
[package_name] [condition] [version]
where [condition] is
=, >=, =<, <, or >
<= and =< should both work, just in case of editing errors.
Version should include the arch and build if using '='. That is the full
Slackware package version designation. 1.1.0-386-1 is valid. 1.1.0 is not.
You can specify multiple packages to satisfy a dependency. The alternate
packages are separated by a pipe, |.
jre = 1.4.1-i586-1 | j2sdk >= 1.4.2-i386-1 | jdk > 1.5.0-i386-1
The package names are case sensitive. So make sure you keep the case of the
package name as it appears in the package filename.
An example slack-required file is present within the slapt-get slack package.
This data will then need to be extracted when the mirrors PACKAGES.TXT file
is generated. See <a href="#slgFAQ17">FAQ #17</a> for an example of how to generate the
PACKAGES.TXT file. The following is an example entry:
PACKAGE NAME: man-pages-1.56-noarch-1.tgz
...(snip)
PACKAGE REQUIRED: man >= 1.5l-i386-1
An example command to pull that data:
tar xzfO pkg-name-version-arch-rel.tgz install/slack-required |xargs -iZ echo -n "Z,"|sed -e "s/,$//"
<a name="slgFAQ20"><b>20. How do I get the newest development version of slapt-get?</b></a>
See the 'Using git' section of the INSTALL document.
<a name="slgFAQ21"><b>21. How can I contribute my ideas or code?</b></a>
Send in ideas or patches to the development list:
slapt-get-devel at software dot jaos dot org
The user list can be used for questions on slapt-get usage, etc:
slapt-get-user at software dot jaos dot org
<a name="slgFAQ22"><b>22. How can I get slapt-get to speak in my native tongue?</b></a>
GNU gettext is used to extract all translatable strings from the source.
Please look in the po/ directory of the slapt-get source. Copy the
slapt-get.pot file to a new file named with your native language abbreviation,
ending in .po. For example, to translate to German, download the current
translation file available here:
http://software.jaos.org/BUILD/slapt-get/po/slapt-get.pot
$ cp slapt-get.pot de.po
Edit that file. For every msgid, translate that into the msgstr "". Leave the
formatting the same.
More translations are needed. Email in your translation to the slapt-get-devel
mailing list (slapt-get-devel at software dot jaos dot org). Your
contributions are greatly appreciated.
<a name="slgFAQ23"><b>23. How do I set the output language?</b></a>
You can change the locale at runtime by setting the LANG environment
variable.
$ LANG=fr slapt-get
<a name="slgFAQ24"><b>24. How do I specify proxy settings?</b></a>
slapt-get takes advantage of the normal http_proxy and ftp_proxy shell
variables. Here are some examples:
# setting the env variables for the entire session
$ export http_proxy=http://host:port
$ export ftp_proxy=ftp://host:port
# just setting them for the current command invocation
$ http_proxy=http://host:port slapt-get --update
If you are using ~/.netrc, libcurl automatically picks up your preferences.
See the netrc(5) manpage for more information.
<a name="slgFAQ25"><b>25. How can I exclude all *pre*, *beta*, and *686* packages safely?</b></a>
An exclude regex like .*pre.* , .*beta.*, or .*686.* may net you the results
of excluding all packages with those characters in the name or version. But
they may also catch packages that have those characters normally occurring in
the package name.
This regex seems to work much better:
[0-9\_\.\-]{1}pre[0-9\-\.\-]{1}
for beta packages:
[0-9\_\.\-]{1}beta[0-9\-\.\-]{1}
or for i686 packages (or for i585 or i486):
[0-9\_\.\-]+i686
Anything matching these regex will be added to the exclude list for the
transaction.
<a name="slgFAQ26"><b>26. How does the transaction engine work?</b></a>
The last few series of releases (0.9.6x and 0.9.7x) have supported
transactions so that nothing happens unless everything checks out properly.
The transaction is built up of packages to install, upgrade and remove. The
transaction status will be reported to the user to be confirmed (unless the
user passes in --no-prompt on the command line). After this confirmation, all
packages will be downloaded before anything else happens. If anything fails
to download, the transaction is immediately aborted. If all packages download
successfully, all removals in the transaction are completed first (in case
packages being installed/upgraded share files with the packages to be removed).
Next, all packages to be installed (new installs) are installed. This should
satisfy dependencies of the packages to be upgraded, which follow after the new
installs. The order of package dependencies, where available, is honored.
These dependencies are installed prior to the packages that require them.
This helps keep your system in a consistent state.
<a name="slgFAQ27"><b>27. How does the package version comparison algorithm work?</b></a>
Say we have foo-1.1.3-i386-1rob and foo-1.1.3-i686-1.
The version parts will be compared, first 1, then 1, then 3. At this point,
both packages are equal, since 1.1.3 == 1.1.3. If one is greater at this
point, the version check returns.
Then, it checks to make sure that both pkgs have the same number of "version
parts". This is the case in this example, both have 3 (1,1,3). This is useful
when you see packages like 1.2 and 1.2.1. Whichever has more parts wins. At
this point, we know if one only has 2 parts, and the other has 3, then the
first two parts of both version strings have to be equal.
Then, the package versions are checked to see if they follow the Slackware
convention. This is determined by checking the first instance of '-' against
the last instance. If the pointer returned from index and rindex are
different, then we assume we have at least two package version separators
(meaning we should have an upstream version, arch, and build at least).
If two separators are found, the build portion of the string is located. The
integer value of the build strings are compared. So "1rob" has an integer
value of 1, and "1" has an integer value of 1. So in our example, both package
versions are the same.
If the only difference is the arch and the packages follow the conventions,
then they should always be equal.
If two separators are not found, then the entire version string from both pkgs
are compared via strcmp. This is a fallback mechanism.
<a name="slgFAQ28"><b>28. I am tracking current, how do I keep the base disk set up to date?</b></a>
If you are tracking current, --dist-upgrade is more appropriate than
--upgrade.
Even if you aren't intentionally switching to a newer distribution,
--dist-upgrade will ensure that the base set is always present while at the
same time keeping your installed packages up to date. See also <a href="#slgFAQ9">FAQ #9</a>.
--dist-upgrade --reinstall can also be useful when some packages in the base
disk set change versions (cxxlibs and sed come to mind). This will reinstall
those base packages that may have lesser version numbers.
--dist-upgrade --remove-obsolete will remove any packages that Pat has removed
from current. CAUTION: this can only take into consideration packages that
are available from your current sources. Thus self made packages will be
considered obsolete as well (they can be excluded within slapt-getrc, however).
Only use this if you have been using Slackware packages exclusively. You can
also use this option for information purposes.
--dist-upgrade --remove-obsolete --reinstall will do all of the above in one
action. It will ensure every package from /a/ is reinstalled, and remove
obsolete packages.
<a name="slgFAQ29"><b>29. How would I script an ldd dependency hack with slapt-get?</b></a>
Do something like the following:
### begin script
#!/bin/sh
# slapt-get wrapper to hack dependencies via ldd where slack-required isn't available
# Copyright (C) 11-30-2003 Jason Woodward <woodwardj at jaos dot org>
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# any later version.
WORKINGDIR=`grep WORKINGDIR /etc/slapt-get/slapt-getrc|cut -f2 -d'='`
MF=MANIFEST
PKGLINES=${WORKINGDIR}/depslapt_pkgs
DEPDATA=()
DEPDATACOUNT=0
function get_pkg_cache_data {
if [ -f ${MF} ]; then rm ${MF};fi
for url in `grep '^SOURCE' /etc/slapt-get/slapt-getrc|cut -f2 -d'='`
do
echo "retrieving data from $url"
if [ -f ${MF}.bz2 ]; then rm ${MF}.bz2;fi
wget -q ${url}/${MF}.bz2
if [ -f ${MF}.bz2 ]; then
bunzip2 -c ${MF}.bz2 >> ${MF}; rm ${MF}.bz2
else
wget -q ${url}/slackware/${MF}.bz2
if [ -f ${MF}.bz2 ]; then bunzip2 -c ${MF}.bz2 >> ${MF}; rm ${MF}.bz2; fi
fi
done
if [ ! -f ${MF} ]; then echo "Failed to download MANIFEST"; exit 1; fi
echo "extracting package data"
grep -n ' Package\: ' ${MF}|awk '{print $1 $3}'|sed -re "s/\|//g" > ${PKGLINES}
}
function map_to_pkg {
LOOKUP=$1
LASTPKG=
for pkgline in `cat ${PKGLINES}|cut -f1 -d':'`
do
if [ $LOOKUP -gt $pkgline ]; then
false
else
LASTPKG=`grep -B 1 $pkgline ${PKGLINES} |head -1|cut -f2 -d':'`
return
fi
done
### clear it in case we get here
LASTPKG=
}
function lookup_lib {
for linenumber in `grep -n $1 $WORKINGDIR/${MF}|cut -f1 -d':'`
do
map_to_pkg $linenumber
if [ -n "$LASTPKG" ]; then
DEPS[$DEPCOUNT]=`basename $LASTPKG|sed -re "s/(.*{1,})\\-(.*[\\.\\-].*[\\.\\-].*).tgz[ ]{0,}$/\1/"`
DEPCOUNT=$((DEPCOUNT + 1))
fi
done
}
function resolve_dependencies {
DEPS=()
DEPCOUNT=0
for pkg in "$@"
do
INST=`ls /var/log/packages/|grep ${pkg}|sort -rn|head -1`
FILES="`cat /var/log/packages/$INST|grep 'bin\/\|lib\/lib.*\.so'|grep -v '\/$'`"
for file in $FILES
do
MISSINGLIBS=`ldd /${file}|grep -i 'not found'|awk '{print $1}'|sort|uniq`
for lib in $MISSINGLIBS
do
echo "Missing lib: $lib"
lookup_lib $lib
done
done
done
### recurse
if [ $DEPCOUNT -gt 0 ]; then
slapt-get --install ${DEPS[*]} || exit
resolve_dependencies ${DEPS[*]}
fi
}
# give usage if no arguments
if [ -z "$1" ]; then echo "Usage: $0 [--update|packages]"; exit; fi
# get package cache data if it is not already there, or we want it
cd ${WORKINGDIR}
if [ "$1" == "--update" ]; then get_pkg_cache_data; exit; fi
if [ ! -f ${PKGLINES} ]; then get_pkg_cache_data; fi
# read pkg data into memory
while read line;do DEPDATA[${DEPDATACOUNT}]=$line; DEPDATACOUNT=$((DEPDATACOUNT + 1)); done < ${PKGLINES}
# install with slapt-get, then call the resolve_dependencies
slapt-get $SLAPT_OPTS --install "$@" || exit
resolve_dependencies $@
### end script
<a name="slgFAQ30"><b>30. Does EXCLUDE work for install as well as upgrade and dist-upgrade?</b></a>
No, EXCLUDE is only consulted for install-set, upgrading, and dist-upgrading.
If you specify the package name as an argument to --install, slapt-get will
ignore the EXCLUDE list.
This does not apply to dependencies. If a dependency of a specified package
is detected, it is checked against the EXCLUDE list. If excluded, the
dependency check for the specified package fails. Override this with
--ignore-dep (to ignore dependency failures).
<a name="slgFAQ31"><b>31. What about package conflicts? How can I specify a conflict for my package?</b></a>
Package conflicts are not as common as dependencies, but just as crucial.
Packages such as lprng and cups sometimes duplicate the same functionality and
must not be installed side by side.
To address this, include within your package ./install/slack-conflicts. This
file has the same syntax as the slack-required file, just without the version
information.
The following is a fictitious example of a lprng slack-conflicts file:
# cat ./install/slack-conflicts
gnome-cups-manager
libgnomecups
cups
#
In this example, we want to specify that the gnome-cups-manager, cups, and
libgnomecups packages are in direct conflict with lprng.
Conflicts will exclude a package during --upgrade or --dist-upgrade. If the
package specified to install is conflicted, the user is prompted to remove
the conflict and install the requested package.
<a name="slgFAQ32"><b>32. Is the ROOT environment variable honored for install and upgrading?</b></a>
Yes, if you have been using ROOT with installpkg and upgradepkg, slapt-get
will modify where it looks for the package logs based on this environment
variable.
For example export ROOT=/home/keary/newroot would make slapt-get look in
/home/keary/newroot/var/log/packages for installed package information and
install all upgraded/new packages in /home/keary/newroot instead of /
All calls to installpkg, removepkg, and upgradepkg will be passed along this
environment variable. See the installpkg(8) manpage.
NOTE: Be sure to run ldconfig -r $ROOT to ensure appropriate library links are
built.
<a name="slgFAQ33"><b>33. How do I specify the exact version of a package to install?</b></a>
Specify the version along with the package name with the --install argument.
For example, to install pkgtools version 9.0.0-i386-1, use 'pkgtools-9.0.0-i386-1'
as the --install argument.
<a name="slgFAQ34"><b>34. Why is upgradepkg complaining it cannot find installpkg or removepkg, with sudo?</b></a>
Right from the sudo man pages Security Notes section:
"Note, however, that the actual PATH environment variable is not modified and
is passed unchanged to the program that sudo executes."
Make sure you include /sbin in your shells PATH environment variable before using
slapt-get via sudo. Or use su - -c 'slapt-get [options] [arg]s'.
<a name="slgFAQ35"><b>35. How can I specify a username/password for the connection to the package source?</b></a>
This can be specified right in the package source URL within the
/etc/slapt-get/slapt-getrc. You will want to make sure that sensitive
passwords are protected, and possibly harden the permissions on
/etc/slapt-get/slapt-getrc so that only the root user can read the file.
Examples:
SOURCE=http://user:[email protected]/path/to/packages/
SOURCE=ftp://user:[email protected]/pub/packages/
<a name="slgFAQ36"><b>36. /var/slapt-get is growing large, how can I safely free up space?</b></a>
Use the --clean option to remove all the cached packages from the tree within
/var/slapt-get.
Or use --autoclean, which is like clean but clears out the local repository of
retrieved package files that can no longer be downloaded, and are largely
useless. This allows a cache to be maintained over a long period without
it growing out of control.
<a name="slgFAQ37"><b>37. What about extra, testing, or pasture packages?</b></a>
Example source entries for the extra, testing, and pasture packages sets can be
found within the example.slapt-getrc file under /usr/doc/slapt-get*/.
<a name="slgFAQ38"><b>38. Can I use slapt-get to mirror packages?</b></a>
Yes, you can use it to mirror packages by using the following:
slapt-get --available|awk '{print $1}'|xargs -r slapt-get --download-only \
--reinstall --install
The packages will then be mirrored under ${ROOT}/var/slapt-get in the
directory structure they where found in. You can then generate the
PACKAGES.TXT and CHECKSUMS.md5 files using the script in <a href="#slgFAQ17">FAQ #17</a> which would
allow you to use this mirror as a slapt-get source.
Optionally, you can set this directory as your WORKINGDIR in order to
avoid copying the package files.
<a name="slgFAQ39"><b>39. Is there a way to use tab completion for the package names in Bash?</b></a>
Yes, this completion was contributed by Alec Thomas on the slapt-get-devel
mailing list. This goes in your ~/.bashrc file (or in /etc/bash_completion,
/etc/bash_completion.d/, /etc/profile, or /etc/profile.d/):
complete_slaptget()
{
cur=${COMP_WORDS[COMP_CWORD]}
if [ "${COMP_WORDS[$[$COMP_CWORD-1]]}" = "--remove" ]; then
COMPREPLY=( $( cd /var/log/packages; ls "$cur"* 2> /dev/null | sed -e 's/-[^-]*-[^-]*-[^-]*$//') )
else
COMPREPLY=( $( slapt-get --search "^$cur" 2> /dev/null | awk '{print $1}' ) )
fi
}
complete -F complete_slaptget -o default slapt-get
<a name="slgFAQ40"><b>40. How do I remove obsoleted packages?</b></a>
If you are tracking current or are dist-upgrading to a new release, you will
encounter packages that you have installed that are no longer required or
part of the basic Slackware install. If you only have the official Slackware
package sources in your slapt-getrc file, then you can do the following:
# slapt-get --remove --remove-obsolete
NOTE: You will want to exclude any packages that are self made so they are
not removed.
<a name="slgFAQ41"><b>41. What provisions have you made for dialup users?</b></a>
The following measurements to save bandwidth have been taken:
* Incomplete package downloads will resume from where they left off.
* ability to set --retry option to specify the number of times to retry
failed downloads.
* The package data download (via --update) will only download those sources
that have changed since the last download, and supports compressed copies
of the data files (PACKAGES.TXT.gz and CHECKSUMS.md5.gz).
* The transaction report gives accurate statistics about sizes required to
download, as well as how much additional space will be required after
unpacking the package archives. This report will also indicate how
much is left to resume if the download was previously interrupted.
<a name="slgFAQ42"><b>42. Is there a way to get a report with the pending updates emailed to me?</b></a>
Yes, you may use these scripts to send notification via email any time updates
are available:
<a href="http://www.nerdworks.org/download/scripts/update-notifier/">http://www.nerdworks.org/download/scripts/update-notifier/</a>
<a href="http://www.aetherstorm.com/slapt_update">http://www.aetherstorm.com/slapt_update</a>
<a name="slgFAQ43"><b>43. What if I don't trust third party sources for upgrades?</b></a>
You can use different slapt-getrc files. For example:
slapt-get --config /etc/slapt-get/slapt-getrc.official --update && \
slapt-get --dist-upgrade
You will have to run --update every time you change your config file if the
WORKINGDIR option is the same between configuration files. Also, if your
excludes and working directory are different in each file, you will want to
specify --config with each invocation of slapt-get to ensure that file is
parsed.
<a name="slgFAQ44"><b>44. How do I specify an addon that is not a dependency of my package?</b></a>
You can include a slack-suggests file within your packages ./install/ directory.
The format of this file follows the slack-required, except version information
is to be left out. This version information is useless as you are just making
a suggestion, not a requirement. If there is a required version of a package
you can either specify it within ./install/slack-required or include it within
the documentation inside of your package.
The suggestion information is presented during the transaction report or via the
--show pkg-name query.
<a name="slgFAQ45"><b>45. Will slapt-get break my system?</b></a>
slapt-get is a frontend to pkgtools. As such you have the same ability to
break a working system using slapt-get as you do using upgradepkg without
caution. A few points are in order:
* slapt-get will not make assumptions or do things without you telling it to,
ie: installing, removing, or upgrading packages
* untested updates are risky, whether using official packages or third party
packages.
* slapt-get will not change your system such that you can only use slapt-get
or are somehow locked into using slapt-get. The only additions to your
system are /etc/slapt-get and /var/slapt-get. You are free to try another
solution or go back to manual upgradepkg.
* UPGRADE.TXT and ChangeLog.txt are still required reading for upgrades or