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
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5052
5053
5054
5055
5056
5057
5058
5059
5060
5061
5062
5063
5064
5065
5066
5067
5068
5069
5070
5071
5072
5073
5074
5075
5076
5077
5078
5079
5080
5081
5082
5083
5084
5085
5086
5087
5088
5089
5090
5091
5092
5093
5094
5095
5096
5097
5098
5099
5100
5101
5102
5103
5104
5105
5106
5107
5108
5109
5110
5111
5112
5113
5114
5115
5116
5117
5118
5119
5120
5121
5122
5123
5124
5125
5126
5127
5128
5129
5130
5131
5132
5133
5134
5135
5136
5137
5138
5139
5140
5141
5142
5143
5144
5145
5146
5147
5148
5149
5150
5151
5152
5153
5154
5155
5156
5157
5158
5159
5160
5161
5162
5163
5164
5165
5166
5167
5168
5169
5170
5171
5172
5173
5174
5175
5176
5177
5178
5179
5180
5181
5182
5183
5184
5185
5186
5187
5188
5189
5190
5191
5192
5193
5194
5195
5196
5197
5198
5199
5200
5201
5202
5203
5204
5205
5206
5207
5208
5209
5210
5211
5212
5213
5214
5215
5216
5217
5218
5219
5220
5221
5222
5223
5224
5225
5226
5227
5228
5229
5230
5231
5232
5233
5234
5235
5236
5237
5238
5239
5240
5241
5242
5243
5244
5245
5246
5247
5248
5249
5250
5251
5252
5253
5254
5255
5256
5257
5258
5259
5260
5261
5262
5263
5264
5265
5266
5267
5268
5269
5270
5271
5272
5273
5274
5275
5276
5277
5278
5279
5280
5281
5282
5283
5284
5285
5286
5287
5288
5289
5290
5291
5292
5293
5294
5295
5296
5297
5298
5299
5300
5301
5302
5303
5304
5305
5306
5307
5308
5309
5310
5311
5312
5313
5314
5315
5316
5317
5318
5319
5320
5321
5322
5323
5324
5325
5326
5327
5328
5329
5330
5331
5332
5333
5334
5335
5336
5337
5338
5339
5340
5341
5342
5343
5344
5345
5346
5347
5348
5349
5350
5351
5352
5353
5354
5355
5356
5357
5358
5359
5360
5361
5362
5363
5364
5365
5366
5367
5368
5369
5370
5371
5372
5373
5374
5375
5376
5377
5378
5379
5380
5381
5382
5383
5384
5385
5386
5387
5388
5389
5390
5391
5392
5393
5394
5395
5396
5397
5398
5399
5400
5401
5402
5403
5404
5405
5406
5407
5408
5409
5410
5411
5412
5413
5414
5415
5416
5417
5418
5419
5420
5421
5422
5423
5424
5425
5426
5427
5428
5429
5430
5431
5432
5433
5434
5435
5436
5437
5438
5439
5440
5441
5442
5443
5444
5445
5446
5447
5448
5449
5450
5451
5452
5453
5454
5455
5456
5457
5458
5459
5460
5461
5462
5463
5464
5465
5466
5467
5468
5469
5470
5471
5472
5473
5474
5475
5476
5477
5478
5479
5480
5481
5482
5483
5484
5485
5486
5487
5488
5489
5490
5491
5492
5493
5494
5495
5496
5497
5498
5499
5500
5501
5502
5503
5504
5505
5506
5507
5508
5509
5510
5511
5512
5513
5514
5515
5516
5517
5518
5519
5520
5521
5522
5523
5524
5525
5526
5527
5528
5529
5530
5531
5532
5533
5534
5535
5536
5537
5538
5539
5540
5541
5542
5543
5544
5545
5546
5547
5548
5549
5550
5551
5552
5553
5554
5555
5556
5557
5558
5559
5560
5561
5562
5563
5564
5565
5566
5567
5568
5569
5570
5571
5572
5573
5574
5575
5576
5577
5578
5579
5580
5581
5582
5583
5584
5585
5586
5587
5588
5589
5590
5591
5592
5593
5594
5595
5596
5597
5598
5599
5600
5601
5602
5603
5604
5605
5606
5607
5608
5609
5610
5611
5612
5613
5614
5615
5616
5617
5618
5619
5620
5621
5622
5623
5624
5625
5626
5627
5628
5629
5630
5631
5632
5633
5634
5635
5636
5637
5638
5639
5640
5641
5642
5643
5644
5645
5646
5647
5648
5649
5650
5651
5652
5653
5654
5655
5656
5657
5658
5659
5660
5661
5662
5663
5664
5665
5666
5667
5668
5669
5670
5671
5672
5673
5674
5675
5676
5677
5678
5679
5680
5681
5682
5683
5684
5685
5686
5687
5688
5689
5690
5691
5692
5693
5694
5695
5696
5697
5698
5699
5700
5701
5702
5703
5704
5705
5706
5707
5708
5709
5710
5711
5712
5713
5714
5715
5716
5717
5718
5719
5720
5721
5722
5723
5724
5725
5726
5727
5728
5729
5730
5731
5732
5733
5734
5735
5736
5737
5738
5739
5740
5741
5742
5743
5744
5745
5746
5747
5748
5749
5750
5751
5752
5753
5754
5755
5756
5757
5758
5759
5760
5761
5762
5763
5764
5765
5766
5767
5768
5769
5770
5771
5772
5773
5774
5775
5776
5777
5778
5779
5780
5781
5782
5783
5784
5785
5786
5787
5788
5789
5790
5791
5792
5793
5794
5795
5796
5797
5798
5799
5800
5801
5802
5803
5804
5805
5806
5807
5808
5809
5810
5811
5812
5813
5814
5815
5816
5817
5818
5819
5820
5821
5822
5823
5824
5825
5826
5827
5828
5829
5830
5831
5832
5833
5834
5835
5836
5837
5838
5839
5840
5841
5842
5843
5844
5845
5846
5847
5848
5849
5850
5851
5852
5853
5854
5855
5856
5857
5858
5859
5860
5861
5862
5863
5864
5865
5866
5867
5868
5869
5870
5871
5872
5873
5874
5875
5876
5877
5878
5879
5880
5881
5882
5883
5884
5885
5886
5887
5888
5889
5890
5891
5892
5893
5894
5895
5896
5897
5898
5899
5900
5901
5902
5903
5904
5905
5906
5907
5908
5909
5910
5911
5912
5913
5914
5915
5916
5917
5918
5919
5920
5921
5922
5923
5924
5925
5926
5927
5928
5929
5930
5931
5932
5933
5934
5935
5936
5937
5938
5939
5940
5941
5942
5943
5944
5945
5946
5947
5948
5949
5950
5951
5952
5953
5954
5955
5956
5957
5958
5959
5960
5961
5962
5963
5964
5965
5966
5967
5968
5969
5970
5971
5972
5973
5974
5975
5976
5977
5978
5979
5980
5981
5982
5983
5984
5985
5986
5987
5988
5989
5990
5991
5992
5993
5994
5995
5996
5997
5998
5999
6000
6001
6002
6003
6004
6005
6006
6007
6008
6009
6010
6011
6012
6013
6014
6015
6016
6017
6018
6019
6020
6021
6022
6023
6024
6025
6026
6027
6028
6029
6030
6031
6032
6033
6034
6035
6036
6037
6038
6039
6040
6041
6042
6043
6044
6045
6046
6047
6048
6049
6050
6051
6052
6053
6054
6055
6056
6057
6058
6059
6060
6061
6062
6063
6064
6065
6066
6067
6068
6069
6070
6071
6072
6073
6074
6075
6076
6077
6078
6079
6080
6081
6082
6083
6084
6085
6086
6087
6088
6089
6090
6091
6092
6093
6094
6095
6096
6097
6098
6099
6100
6101
6102
6103
6104
6105
6106
6107
6108
6109
6110
6111
6112
6113
6114
6115
6116
6117
6118
6119
6120
6121
6122
6123
6124
6125
6126
6127
6128
6129
6130
6131
6132
6133
6134
6135
6136
6137
6138
6139
6140
6141
6142
6143
6144
6145
6146
6147
6148
6149
6150
6151
6152
6153
6154
6155
6156
6157
6158
6159
6160
6161
6162
6163
6164
6165
6166
6167
6168
6169
6170
6171
6172
6173
6174
6175
6176
6177
6178
6179
6180
6181
6182
6183
6184
6185
6186
6187
6188
6189
6190
6191
6192
6193
6194
6195
6196
6197
6198
6199
6200
6201
6202
6203
6204
6205
6206
6207
6208
6209
6210
6211
6212
6213
6214
6215
6216
6217
6218
6219
6220
6221
6222
6223
6224
6225
6226
6227
6228
6229
6230
6231
6232
6233
6234
6235
6236
6237
6238
6239
6240
6241
6242
6243
6244
6245
6246
6247
6248
6249
6250
6251
6252
6253
6254
6255
6256
6257
6258
6259
6260
6261
6262
6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
6273
6274
6275
6276
6277
6278
6279
6280
6281
6282
6283
6284
6285
6286
6287
6288
6289
6290
6291
6292
6293
6294
6295
6296
6297
6298
6299
6300
6301
6302
6303
6304
6305
6306
6307
6308
6309
6310
6311
6312
6313
6314
6315
6316
6317
6318
6319
6320
6321
6322
6323
6324
6325
6326
6327
6328
6329
6330
6331
6332
6333
6334
6335
6336
6337
6338
6339
6340
6341
6342
6343
6344
6345
6346
6347
6348
6349
6350
6351
6352
6353
6354
6355
6356
6357
6358
6359
6360
6361
6362
6363
6364
6365
6366
6367
6368
6369
6370
6371
6372
6373
6374
6375
6376
6377
6378
6379
6380
6381
6382
6383
6384
6385
6386
6387
6388
6389
6390
6391
6392
6393
6394
6395
6396
6397
6398
6399
6400
6401
6402
6403
6404
6405
6406
6407
6408
6409
6410
6411
6412
6413
6414
6415
6416
6417
6418
6419
6420
6421
6422
6423
6424
6425
6426
6427
6428
6429
6430
6431
6432
6433
6434
6435
6436
6437
6438
6439
6440
6441
6442
6443
6444
6445
6446
6447
6448
6449
6450
6451
6452
6453
6454
6455
6456
6457
6458
6459
6460
6461
6462
6463
6464
6465
6466
6467
6468
6469
6470
6471
6472
6473
6474
6475
6476
6477
6478
6479
6480
6481
6482
6483
6484
6485
6486
6487
6488
6489
6490
6491
6492
6493
6494
6495
6496
6497
6498
6499
6500
6501
6502
6503
6504
6505
6506
6507
6508
6509
6510
6511
6512
6513
6514
6515
6516
6517
6518
6519
6520
6521
6522
6523
6524
6525
6526
6527
6528
6529
6530
6531
6532
6533
6534
6535
6536
6537
6538
6539
6540
6541
6542
6543
6544
6545
6546
6547
6548
6549
6550
6551
6552
6553
6554
6555
6556
6557
6558
6559
6560
6561
6562
6563
6564
6565
6566
6567
6568
6569
6570
6571
6572
6573
6574
6575
6576
6577
6578
6579
6580
6581
6582
6583
6584
6585
6586
6587
6588
6589
6590
6591
6592
6593
6594
6595
6596
6597
6598
6599
6600
6601
6602
6603
6604
6605
6606
6607
6608
6609
6610
6611
6612
6613
6614
6615
6616
6617
6618
6619
6620
6621
6622
6623
6624
6625
6626
6627
6628
6629
6630
6631
6632
6633
6634
6635
6636
6637
6638
6639
6640
6641
6642
6643
6644
6645
6646
6647
6648
6649
6650
6651
6652
6653
6654
6655
6656
6657
6658
6659
6660
6661
6662
6663
6664
6665
6666
6667
6668
6669
6670
6671
6672
6673
6674
6675
6676
6677
6678
6679
6680
6681
6682
6683
6684
6685
6686
6687
6688
6689
6690
6691
6692
6693
6694
6695
6696
6697
6698
6699
6700
6701
6702
6703
6704
6705
6706
6707
6708
6709
6710
6711
6712
6713
6714
6715
6716
6717
6718
6719
6720
6721
6722
6723
6724
6725
6726
6727
6728
6729
6730
6731
6732
6733
6734
6735
6736
6737
6738
6739
6740
6741
6742
6743
6744
6745
6746
6747
6748
6749
6750
6751
6752
6753
6754
6755
6756
6757
6758
6759
6760
6761
6762
6763
6764
6765
6766
6767
6768
6769
6770
6771
6772
6773
6774
6775
6776
6777
6778
6779
6780
6781
6782
6783
6784
6785
6786
6787
6788
6789
6790
6791
6792
6793
6794
6795
6796
6797
6798
6799
6800
6801
6802
6803
6804
6805
6806
6807
6808
6809
6810
6811
6812
6813
6814
6815
6816
6817
6818
6819
6820
6821
6822
6823
6824
6825
6826
6827
6828
6829
6830
6831
6832
6833
6834
6835
6836
6837
6838
6839
6840
6841
6842
6843
6844
6845
6846
6847
6848
6849
6850
6851
6852
6853
6854
6855
6856
6857
6858
6859
6860
6861
6862
6863
6864
6865
6866
6867
6868
6869
6870
6871
6872
6873
6874
6875
6876
6877
6878
6879
6880
6881
6882
6883
6884
6885
6886
6887
6888
6889
6890
6891
6892
6893
6894
6895
6896
6897
6898
6899
6900
6901
6902
6903
6904
6905
6906
6907
6908
6909
6910
6911
6912
6913
6914
6915
6916
6917
6918
6919
6920
6921
6922
6923
6924
6925
6926
6927
6928
6929
6930
6931
6932
6933
6934
6935
6936
6937
6938
6939
6940
6941
6942
6943
6944
6945
6946
6947
6948
6949
6950
6951
6952
6953
6954
6955
6956
6957
6958
6959
6960
6961
6962
6963
6964
6965
6966
6967
6968
6969
6970
6971
6972
6973
6974
6975
6976
6977
6978
6979
6980
6981
6982
6983
6984
6985
6986
6987
6988
6989
6990
6991
6992
6993
6994
6995
6996
6997
6998
6999
7000
7001
7002
7003
7004
7005
7006
7007
7008
7009
7010
7011
7012
7013
7014
7015
7016
7017
7018
7019
7020
7021
7022
7023
7024
7025
7026
7027
7028
7029
7030
7031
7032
7033
7034
7035
7036
7037
7038
7039
7040
7041
7042
7043
7044
7045
7046
7047
7048
7049
7050
7051
7052
7053
7054
7055
7056
7057
7058
7059
7060
7061
7062
7063
7064
7065
7066
7067
7068
7069
7070
7071
7072
7073
7074
7075
7076
7077
7078
7079
7080
7081
7082
7083
7084
7085
7086
7087
7088
7089
7090
7091
7092
7093
7094
7095
7096
7097
7098
7099
7100
7101
7102
7103
7104
7105
7106
7107
7108
7109
7110
7111
7112
7113
7114
7115
7116
7117
7118
7119
7120
7121
7122
7123
7124
7125
7126
7127
7128
7129
7130
7131
7132
7133
7134
7135
7136
7137
7138
7139
7140
7141
7142
7143
7144
7145
7146
7147
7148
7149
7150
7151
7152
7153
7154
7155
7156
7157
7158
7159
7160
7161
7162
7163
7164
7165
7166
7167
7168
7169
7170
7171
7172
7173
7174
7175
7176
7177
7178
7179
7180
7181
7182
7183
7184
7185
7186
7187
7188
7189
7190
7191
7192
7193
7194
7195
7196
7197
7198
7199
7200
7201
7202
7203
7204
7205
7206
7207
7208
7209
7210
7211
7212
7213
7214
7215
7216
7217
7218
7219
7220
7221
7222
7223
7224
7225
7226
7227
7228
7229
7230
7231
7232
7233
7234
7235
7236
7237
7238
7239
7240
7241
7242
7243
7244
7245
7246
7247
7248
7249
7250
7251
7252
7253
7254
7255
7256
7257
7258
7259
7260
7261
7262
7263
7264
7265
7266
7267
7268
7269
7270
7271
7272
7273
7274
7275
7276
7277
7278
7279
7280
7281
7282
7283
7284
7285
7286
7287
7288
7289
7290
7291
7292
7293
7294
7295
7296
7297
7298
7299
7300
7301
7302
7303
7304
7305
7306
7307
7308
7309
7310
7311
7312
7313
7314
7315
7316
7317
7318
7319
7320
7321
7322
7323
7324
7325
7326
7327
7328
7329
7330
7331
7332
7333
7334
7335
7336
7337
7338
7339
7340
7341
7342
7343
7344
7345
7346
7347
7348
7349
7350
7351
7352
7353
7354
7355
7356
7357
7358
7359
7360
7361
7362
7363
7364
7365
7366
7367
7368
7369
7370
7371
7372
7373
7374
7375
7376
7377
7378
7379
7380
7381
7382
7383
7384
7385
7386
7387
7388
7389
7390
7391
7392
7393
7394
7395
7396
7397
7398
7399
7400
7401
7402
7403
7404
7405
7406
7407
7408
7409
7410
7411
7412
7413
7414
7415
7416
7417
7418
7419
7420
7421
7422
7423
7424
7425
7426
7427
7428
7429
7430
7431
7432
7433
7434
7435
7436
7437
7438
7439
7440
7441
7442
7443
7444
7445
7446
7447
7448
7449
7450
7451
7452
7453
7454
7455
7456
7457
7458
7459
7460
7461
7462
7463
7464
7465
7466
7467
7468
7469
7470
7471
7472
7473
7474
7475
7476
7477
7478
7479
7480
7481
7482
7483
7484
7485
7486
7487
7488
7489
7490
7491
7492
7493
7494
7495
7496
7497
7498
7499
7500
7501
7502
7503
7504
7505
7506
7507
7508
7509
7510
7511
7512
7513
7514
7515
7516
7517
7518
7519
7520
7521
7522
7523
7524
7525
7526
7527
7528
7529
7530
7531
7532
7533
7534
7535
7536
7537
7538
7539
7540
7541
7542
7543
7544
7545
7546
7547
7548
7549
7550
7551
7552
7553
7554
7555
7556
7557
7558
7559
7560
7561
7562
7563
7564
7565
7566
7567
7568
7569
7570
7571
7572
7573
7574
7575
7576
7577
7578
7579
7580
7581
7582
7583
7584
7585
7586
7587
7588
7589
7590
7591
7592
7593
7594
7595
7596
7597
7598
7599
7600
7601
7602
7603
7604
7605
7606
7607
7608
7609
7610
7611
7612
7613
7614
7615
7616
7617
7618
7619
7620
7621
7622
7623
7624
7625
7626
7627
7628
7629
7630
7631
7632
7633
7634
7635
7636
7637
7638
7639
7640
7641
7642
7643
7644
7645
7646
7647
7648
7649
7650
7651
7652
7653
7654
7655
7656
7657
7658
7659
7660
7661
7662
7663
7664
7665
7666
7667
7668
7669
7670
7671
7672
7673
7674
7675
7676
7677
7678
7679
7680
7681
7682
7683
7684
7685
7686
7687
7688
7689
7690
7691
7692
7693
7694
7695
7696
7697
7698
7699
7700
7701
7702
7703
7704
7705
7706
7707
7708
7709
7710
7711
7712
7713
7714
7715
7716
7717
7718
7719
7720
7721
7722
7723
7724
7725
7726
7727
7728
7729
7730
7731
7732
7733
7734
7735
7736
7737
7738
7739
7740
7741
7742
7743
7744
7745
7746
7747
7748
7749
7750
7751
7752
7753
7754
7755
7756
7757
7758
7759
7760
7761
7762
7763
7764
7765
7766
7767
7768
7769
7770
7771
7772
7773
7774
7775
7776
7777
7778
7779
7780
7781
7782
7783
7784
7785
7786
7787
7788
7789
7790
7791
7792
7793
7794
7795
7796
7797
7798
7799
7800
7801
7802
7803
7804
7805
7806
7807
7808
7809
7810
7811
7812
7813
7814
7815
7816
7817
7818
7819
7820
7821
7822
7823
7824
7825
7826
7827
7828
7829
7830
7831
7832
7833
7834
7835
7836
7837
7838
7839
7840
7841
7842
7843
7844
7845
7846
7847
7848
7849
7850
7851
7852
7853
7854
7855
7856
7857
7858
7859
7860
7861
7862
7863
7864
7865
7866
7867
7868
7869
7870
7871
7872
7873
7874
7875
7876
7877
7878
7879
7880
7881
7882
7883
7884
7885
7886
7887
7888
7889
7890
7891
7892
7893
7894
7895
7896
7897
7898
7899
7900
7901
7902
7903
7904
7905
7906
7907
7908
7909
7910
7911
7912
7913
7914
7915
7916
7917
7918
7919
7920
7921
7922
7923
7924
7925
7926
7927
7928
7929
7930
7931
7932
7933
7934
7935
7936
7937
7938
7939
7940
7941
7942
7943
7944
7945
7946
7947
7948
7949
7950
7951
7952
7953
7954
7955
7956
7957
7958
7959
7960
7961
7962
7963
7964
7965
7966
7967
7968
7969
7970
7971
7972
7973
7974
7975
7976
7977
7978
7979
7980
7981
7982
7983
7984
7985
7986
7987
7988
7989
7990
7991
7992
7993
7994
7995
7996
7997
7998
7999
8000
8001
8002
8003
8004
8005
8006
8007
8008
8009
8010
8011
8012
8013
8014
8015
8016
8017
8018
8019
8020
8021
8022
8023
8024
8025
8026
8027
8028
8029
8030
8031
8032
8033
8034
8035
8036
8037
8038
8039
8040
8041
8042
8043
8044
8045
8046
8047
8048
8049
8050
8051
8052
8053
8054
8055
8056
8057
8058
8059
8060
8061
8062
8063
8064
8065
8066
8067
8068
8069
8070
8071
8072
8073
8074
8075
8076
8077
8078
8079
8080
8081
8082
8083
8084
8085
8086
8087
8088
8089
8090
8091
8092
8093
8094
8095
8096
8097
8098
8099
8100
8101
8102
8103
8104
8105
8106
8107
8108
8109
8110
8111
8112
8113
8114
8115
8116
8117
8118
8119
8120
8121
8122
8123
8124
8125
8126
8127
8128
8129
8130
8131
8132
8133
8134
8135
8136
8137
8138
8139
8140
8141
8142
8143
8144
8145
8146
8147
8148
8149
8150
8151
8152
8153
8154
8155
8156
8157
8158
8159
8160
8161
8162
8163
8164
8165
8166
8167
8168
8169
8170
8171
8172
8173
8174
8175
8176
8177
8178
8179
8180
8181
8182
8183
8184
8185
8186
8187
8188
8189
8190
8191
8192
8193
8194
8195
8196
8197
8198
8199
8200
8201
8202
8203
8204
8205
8206
8207
8208
8209
8210
8211
8212
8213
8214
8215
8216
8217
8218
8219
8220
8221
8222
8223
8224
8225
8226
8227
8228
8229
8230
8231
8232
8233
8234
8235
8236
8237
8238
8239
8240
8241
8242
8243
8244
8245
8246
8247
8248
8249
8250
8251
8252
8253
8254
8255
8256
8257
8258
8259
8260
8261
8262
8263
8264
8265
8266
8267
8268
8269
8270
8271
8272
8273
8274
8275
8276
8277
8278
8279
8280
8281
8282
8283
8284
8285
8286
8287
8288
8289
8290
8291
8292
8293
8294
8295
8296
8297
8298
8299
8300
8301
8302
8303
8304
8305
8306
8307
8308
8309
8310
8311
8312
8313
8314
8315
8316
8317
8318
8319
8320
8321
8322
8323
8324
8325
8326
8327
8328
8329
8330
8331
8332
8333
8334
8335
8336
8337
8338
8339
8340
8341
8342
8343
8344
8345
8346
8347
8348
8349
8350
8351
8352
8353
8354
8355
8356
8357
8358
8359
8360
8361
8362
8363
8364
8365
8366
8367
8368
8369
8370
8371
8372
8373
8374
8375
8376
8377
8378
8379
8380
8381
8382
8383
8384
8385
8386
8387
8388
8389
8390
8391
8392
8393
8394
8395
8396
8397
8398
8399
8400
8401
8402
8403
8404
8405
8406
8407
8408
8409
8410
8411
8412
8413
8414
8415
8416
8417
8418
8419
8420
8421
8422
8423
8424
8425
8426
8427
8428
8429
8430
8431
8432
8433
8434
8435
8436
8437
8438
8439
8440
8441
8442
8443
8444
8445
8446
8447
8448
8449
8450
8451
8452
8453
8454
8455
8456
8457
8458
8459
8460
8461
8462
8463
8464
8465
8466
8467
8468
8469
8470
8471
8472
8473
8474
8475
8476
8477
8478
8479
8480
8481
8482
8483
8484
8485
8486
8487
8488
8489
8490
8491
8492
8493
8494
8495
8496
8497
8498
8499
8500
8501
8502
8503
8504
8505
8506
8507
8508
8509
8510
8511
8512
8513
8514
8515
8516
8517
8518
8519
8520
8521
8522
8523
8524
8525
8526
8527
8528
8529
8530
8531
8532
8533
8534
8535
8536
8537
8538
8539
8540
8541
8542
8543
8544
8545
8546
8547
8548
8549
8550
8551
8552
8553
8554
8555
8556
8557
8558
8559
8560
8561
8562
8563
8564
8565
8566
8567
8568
8569
8570
8571
8572
8573
8574
8575
8576
8577
8578
8579
8580
8581
8582
8583
8584
8585
8586
8587
8588
8589
8590
8591
8592
8593
8594
8595
8596
8597
8598
8599
8600
8601
8602
8603
8604
8605
8606
8607
8608
8609
8610
8611
8612
8613
8614
8615
8616
8617
8618
8619
8620
8621
8622
8623
8624
8625
8626
8627
8628
8629
8630
8631
8632
8633
8634
8635
8636
8637
8638
8639
8640
8641
8642
8643
8644
8645
8646
8647
8648
8649
8650
8651
8652
8653
8654
8655
8656
8657
8658
8659
8660
8661
8662
8663
8664
8665
8666
8667
8668
8669
8670
8671
8672
8673
8674
8675
8676
8677
8678
8679
8680
8681
8682
8683
8684
8685
8686
8687
8688
8689
8690
8691
8692
8693
8694
8695
8696
8697
8698
8699
8700
8701
8702
8703
8704
8705
8706
8707
8708
8709
8710
8711
8712
8713
8714
8715
8716
8717
8718
8719
8720
8721
8722
8723
8724
8725
8726
8727
8728
8729
8730
8731
8732
8733
8734
8735
8736
8737
8738
8739
8740
8741
8742
8743
8744
8745
8746
8747
8748
8749
8750
8751
8752
8753
8754
8755
8756
8757
8758
8759
8760
8761
8762
8763
8764
8765
8766
8767
8768
8769
8770
8771
8772
8773
8774
8775
8776
8777
8778
8779
8780
8781
8782
8783
8784
8785
8786
8787
8788
8789
8790
8791
8792
8793
8794
8795
8796
8797
8798
8799
8800
8801
8802
8803
8804
8805
8806
8807
8808
8809
8810
8811
8812
8813
8814
8815
8816
8817
8818
8819
8820
8821
8822
8823
8824
8825
8826
8827
8828
8829
8830
8831
8832
8833
8834
8835
8836
8837
8838
8839
8840
8841
8842
8843
8844
8845
8846
8847
8848
8849
8850
8851
8852
8853
8854
8855
8856
8857
8858
8859
8860
8861
8862
8863
8864
8865
8866
8867
8868
8869
8870
8871
8872
8873
8874
8875
8876
8877
8878
8879
8880
8881
8882
8883
8884
8885
8886
8887
8888
8889
8890
8891
8892
8893
8894
8895
8896
8897
8898
8899
8900
8901
8902
8903
8904
8905
8906
8907
8908
8909
8910
8911
8912
8913
8914
8915
8916
8917
8918
8919
8920
8921
8922
8923
8924
8925
8926
8927
8928
8929
8930
8931
8932
8933
8934
8935
8936
8937
8938
8939
8940
8941
8942
8943
8944
8945
8946
8947
8948
8949
8950
8951
8952
8953
8954
8955
8956
8957
8958
8959
8960
8961
8962
8963
8964
8965
8966
8967
8968
8969
8970
8971
8972
8973
8974
8975
8976
8977
8978
8979
8980
8981
8982
8983
8984
8985
8986
8987
8988
8989
8990
8991
8992
8993
8994
8995
8996
8997
8998
8999
9000
9001
9002
9003
9004
9005
9006
9007
9008
9009
9010
9011
9012
9013
9014
9015
9016
9017
9018
9019
9020
9021
9022
9023
9024
9025
9026
9027
9028
9029
9030
9031
9032
9033
9034
9035
9036
9037
9038
9039
9040
9041
9042
9043
9044
9045
9046
9047
9048
9049
9050
9051
9052
9053
9054
9055
9056
9057
9058
9059
9060
9061
9062
9063
9064
9065
9066
9067
9068
9069
9070
9071
9072
9073
9074
9075
9076
9077
9078
9079
9080
9081
9082
9083
9084
9085
9086
9087
9088
9089
9090
9091
9092
9093
9094
9095
9096
9097
9098
9099
9100
9101
9102
9103
9104
9105
9106
9107
9108
9109
9110
9111
9112
9113
9114
9115
9116
9117
9118
9119
9120
9121
9122
9123
9124
9125
9126
9127
9128
9129
9130
9131
9132
9133
9134
9135
9136
9137
9138
9139
9140
9141
9142
9143
9144
9145
9146
9147
9148
9149
9150
9151
9152
9153
9154
9155
9156
9157
9158
9159
9160
9161
9162
9163
9164
9165
9166
9167
9168
9169
9170
9171
9172
9173
9174
9175
9176
9177
9178
9179
9180
9181
9182
9183
9184
9185
9186
9187
9188
9189
9190
9191
9192
9193
9194
9195
9196
9197
9198
9199
9200
9201
9202
9203
9204
9205
9206
9207
9208
9209
9210
9211
9212
9213
9214
9215
9216
9217
9218
9219
9220
9221
9222
9223
9224
9225
9226
9227
9228
9229
9230
9231
9232
9233
9234
9235
9236
9237
9238
9239
9240
9241
9242
9243
9244
9245
9246
9247
9248
9249
9250
9251
9252
9253
9254
9255
9256
9257
9258
9259
9260
9261
9262
9263
9264
9265
9266
9267
9268
9269
9270
9271
9272
9273
9274
9275
9276
9277
9278
9279
9280
9281
9282
9283
9284
9285
9286
9287
9288
9289
9290
9291
9292
9293
9294
9295
9296
9297
9298
9299
9300
9301
9302
9303
9304
9305
9306
9307
9308
9309
9310
9311
9312
9313
9314
9315
9316
9317
9318
9319
9320
9321
9322
9323
9324
9325
9326
9327
9328
9329
9330
9331
9332
9333
9334
9335
9336
9337
9338
9339
9340
9341
9342
9343
9344
9345
9346
9347
9348
9349
9350
9351
9352
9353
9354
9355
9356
9357
9358
9359
9360
9361
9362
9363
9364
9365
9366
9367
9368
9369
9370
9371
9372
9373
9374
9375
9376
9377
9378
9379
9380
9381
9382
9383
9384
9385
9386
9387
9388
9389
9390
9391
9392
9393
9394
9395
9396
9397
9398
9399
9400
9401
9402
9403
9404
9405
9406
9407
9408
9409
9410
9411
9412
9413
9414
9415
9416
9417
9418
9419
9420
9421
9422
9423
9424
9425
9426
9427
9428
9429
9430
9431
9432
9433
9434
9435
9436
9437
9438
9439
9440
9441
9442
9443
9444
9445
9446
9447
9448
9449
9450
9451
9452
9453
9454
9455
9456
9457
9458
9459
9460
9461
9462
9463
9464
9465
9466
9467
9468
9469
9470
9471
9472
9473
9474
9475
9476
9477
9478
9479
9480
9481
9482
9483
9484
9485
9486
9487
9488
9489
9490
9491
9492
9493
9494
9495
9496
9497
9498
9499
9500
9501
9502
9503
9504
9505
9506
9507
9508
9509
9510
9511
9512
9513
9514
9515
9516
9517
9518
9519
9520
9521
9522
9523
9524
9525
9526
9527
9528
9529
9530
9531
9532
9533
9534
9535
9536
9537
9538
9539
9540
9541
9542
9543
9544
9545
9546
9547
9548
9549
9550
9551
9552
9553
9554
9555
9556
9557
9558
9559
9560
9561
9562
9563
9564
9565
9566
9567
9568
9569
9570
9571
9572
9573
9574
9575
9576
9577
9578
9579
9580
9581
9582
9583
9584
9585
9586
9587
9588
9589
9590
9591
9592
9593
9594
9595
9596
9597
9598
9599
9600
9601
9602
9603
9604
9605
9606
9607
9608
9609
9610
9611
9612
9613
9614
9615
9616
9617
9618
9619
9620
9621
9622
9623
9624
9625
9626
9627
9628
9629
9630
9631
9632
9633
9634
9635
9636
9637
9638
9639
9640
9641
9642
9643
9644
9645
9646
9647
9648
9649
9650
9651
9652
9653
9654
9655
9656
9657
9658
9659
9660
9661
9662
9663
9664
9665
9666
9667
9668
9669
9670
9671
9672
9673
9674
9675
9676
9677
9678
9679
9680
9681
9682
9683
9684
9685
9686
9687
9688
9689
9690
9691
9692
9693
9694
9695
9696
9697
9698
9699
9700
9701
9702
9703
9704
9705
9706
9707
9708
9709
9710
9711
9712
9713
9714
9715
9716
9717
9718
9719
9720
9721
9722
9723
9724
9725
9726
9727
9728
9729
9730
9731
9732
9733
9734
9735
9736
9737
9738
9739
9740
9741
9742
9743
9744
9745
9746
9747
9748
9749
9750
9751
9752
9753
9754
9755
9756
9757
9758
9759
9760
9761
9762
9763
9764
9765
9766
9767
9768
9769
9770
9771
9772
9773
9774
9775
9776
9777
9778
9779
9780
9781
9782
9783
9784
9785
9786
9787
9788
9789
9790
9791
9792
9793
9794
9795
9796
9797
9798
9799
9800
9801
9802
9803
9804
9805
9806
9807
9808
9809
9810
9811
9812
9813
9814
9815
9816
9817
9818
9819
9820
9821
9822
9823
9824
9825
9826
9827
9828
9829
9830
9831
9832
9833
9834
9835
9836
9837
9838
9839
9840
9841
9842
9843
9844
9845
9846
9847
9848
9849
9850
9851
9852
9853
9854
9855
9856
9857
9858
9859
9860
9861
9862
9863
9864
9865
9866
9867
9868
9869
9870
9871
9872
9873
9874
9875
9876
9877
9878
9879
9880
9881
9882
9883
9884
9885
9886
9887
9888
9889
9890
9891
9892
9893
9894
9895
9896
9897
9898
9899
9900
9901
9902
9903
9904
9905
9906
9907
9908
9909
9910
9911
9912
9913
9914
9915
9916
9917
9918
9919
9920
9921
9922
9923
9924
9925
9926
9927
9928
9929
9930
9931
9932
9933
9934
9935
9936
9937
9938
9939
9940
9941
9942
9943
9944
9945
9946
9947
9948
9949
9950
9951
9952
9953
9954
9955
9956
9957
9958
9959
9960
9961
9962
9963
9964
9965
9966
9967
9968
9969
9970
9971
9972
9973
9974
9975
9976
9977
9978
9979
9980
9981
9982
9983
9984
9985
9986
9987
9988
9989
9990
9991
9992
9993
9994
9995
9996
9997
9998
9999
10000
10001
10002
10003
10004
10005
10006
10007
10008
10009
10010
10011
10012
10013
10014
10015
10016
10017
10018
10019
10020
10021
10022
10023
10024
10025
10026
10027
10028
10029
10030
10031
10032
10033
10034
10035
10036
10037
10038
10039
10040
10041
10042
10043
10044
10045
10046
10047
10048
10049
10050
10051
10052
10053
10054
10055
10056
10057
10058
10059
10060
10061
10062
10063
10064
10065
10066
10067
10068
10069
10070
10071
10072
10073
10074
10075
10076
10077
10078
10079
10080
10081
10082
10083
10084
10085
10086
10087
10088
10089
10090
10091
10092
10093
10094
10095
10096
10097
10098
10099
10100
10101
10102
10103
10104
10105
10106
10107
10108
10109
10110
10111
10112
10113
10114
10115
10116
10117
10118
10119
10120
10121
10122
10123
10124
10125
10126
10127
10128
10129
10130
10131
10132
10133
10134
10135
10136
10137
10138
10139
10140
10141
10142
10143
10144
10145
10146
10147
10148
10149
10150
10151
10152
10153
10154
10155
10156
10157
10158
10159
10160
10161
10162
10163
10164
10165
10166
10167
10168
10169
10170
10171
10172
10173
10174
10175
10176
10177
10178
10179
10180
10181
10182
10183
10184
10185
10186
10187
10188
10189
10190
10191
10192
10193
10194
10195
10196
10197
10198
10199
10200
10201
10202
10203
10204
10205
10206
10207
10208
10209
10210
10211
10212
10213
10214
10215
10216
10217
10218
10219
10220
10221
10222
10223
10224
10225
10226
10227
10228
10229
10230
10231
10232
10233
10234
10235
10236
10237
10238
10239
10240
10241
10242
10243
10244
10245
10246
10247
10248
10249
10250
10251
10252
10253
10254
10255
10256
10257
10258
10259
10260
10261
10262
10263
10264
10265
10266
10267
10268
10269
10270
10271
10272
10273
10274
10275
10276
10277
10278
10279
10280
10281
10282
10283
10284
10285
10286
10287
10288
10289
10290
10291
10292
10293
10294
10295
10296
10297
10298
10299
10300
10301
10302
10303
10304
10305
10306
10307
10308
10309
10310
10311
10312
10313
10314
10315
10316
10317
10318
10319
10320
10321
10322
10323
10324
10325
10326
10327
10328
10329
10330
10331
10332
10333
10334
10335
10336
10337
10338
10339
10340
10341
10342
10343
10344
10345
10346
10347
10348
10349
10350
10351
10352
10353
10354
10355
10356
10357
10358
10359
10360
10361
10362
10363
10364
10365
10366
10367
10368
10369
10370
10371
10372
10373
10374
10375
10376
10377
10378
10379
10380
10381
10382
10383
10384
10385
10386
10387
10388
10389
10390
10391
10392
10393
10394
10395
10396
10397
10398
10399
10400
10401
10402
10403
10404
10405
10406
10407
10408
10409
10410
10411
10412
10413
10414
10415
10416
10417
10418
10419
10420
10421
10422
10423
10424
10425
10426
10427
10428
10429
10430
10431
10432
10433
10434
10435
10436
10437
10438
10439
10440
10441
10442
10443
10444
10445
10446
10447
10448
10449
10450
10451
10452
10453
10454
10455
10456
10457
10458
10459
10460
10461
10462
10463
10464
10465
10466
10467
10468
10469
10470
10471
10472
10473
10474
10475
10476
10477
10478
10479
10480
10481
10482
10483
10484
10485
10486
10487
10488
10489
10490
10491
10492
10493
10494
10495
10496
10497
10498
10499
10500
10501
10502
10503
10504
10505
10506
10507
10508
10509
10510
10511
10512
10513
10514
10515
10516
10517
10518
10519
10520
10521
10522
10523
10524
10525
10526
10527
10528
10529
10530
10531
10532
10533
10534
10535
10536
10537
10538
10539
10540
10541
10542
10543
10544
10545
10546
10547
10548
10549
10550
10551
10552
10553
10554
10555
10556
10557
10558
10559
10560
10561
10562
10563
10564
10565
10566
10567
10568
10569
10570
10571
10572
10573
10574
10575
10576
10577
10578
10579
10580
10581
10582
10583
10584
10585
10586
10587
10588
10589
10590
10591
10592
10593
10594
10595
10596
10597
10598
10599
10600
10601
10602
10603
10604
10605
10606
10607
10608
10609
10610
10611
10612
10613
10614
10615
10616
10617
10618
10619
10620
10621
10622
10623
10624
10625
10626
10627
10628
10629
10630
10631
10632
10633
10634
10635
10636
10637
10638
10639
10640
10641
10642
10643
10644
10645
10646
10647
10648
10649
10650
10651
10652
10653
10654
10655
10656
10657
10658
10659
10660
10661
10662
10663
10664
10665
10666
10667
10668
10669
10670
10671
10672
10673
10674
10675
10676
10677
10678
10679
10680
10681
10682
10683
10684
10685
10686
10687
10688
10689
10690
10691
10692
10693
10694
10695
10696
10697
10698
10699
10700
10701
10702
10703
10704
10705
10706
10707
10708
10709
10710
10711
10712
10713
10714
10715
10716
10717
10718
10719
10720
10721
10722
10723
10724
10725
10726
10727
10728
10729
10730
10731
10732
10733
10734
10735
10736
10737
10738
10739
10740
10741
10742
10743
10744
10745
10746
10747
10748
10749
10750
10751
10752
10753
10754
10755
10756
10757
10758
10759
10760
10761
10762
10763
10764
10765
10766
10767
10768
10769
10770
10771
10772
10773
10774
10775
10776
10777
10778
10779
10780
10781
10782
10783
10784
10785
10786
10787
10788
10789
10790
10791
10792
10793
10794
10795
10796
10797
10798
10799
10800
10801
10802
10803
10804
10805
10806
10807
10808
10809
10810
10811
10812
10813
10814
10815
10816
10817
10818
10819
10820
10821
10822
10823
10824
10825
10826
10827
10828
10829
10830
10831
10832
10833
10834
10835
10836
10837
10838
10839
10840
10841
10842
10843
10844
10845
10846
10847
10848
10849
10850
10851
10852
10853
10854
10855
10856
10857
10858
10859
10860
10861
10862
10863
10864
10865
10866
10867
10868
10869
10870
10871
10872
10873
10874
10875
10876
10877
10878
10879
10880
10881
10882
10883
10884
10885
10886
10887
10888
10889
10890
10891
10892
10893
10894
10895
10896
10897
10898
10899
10900
10901
10902
10903
10904
10905
10906
10907
10908
10909
10910
10911
10912
10913
10914
10915
10916
10917
10918
10919
10920
10921
10922
10923
10924
10925
10926
10927
10928
10929
10930
10931
10932
10933
10934
10935
10936
10937
10938
10939
10940
10941
10942
10943
10944
10945
10946
10947
10948
10949
10950
10951
10952
10953
10954
10955
10956
10957
10958
10959
10960
10961
10962
10963
10964
10965
10966
10967
10968
10969
10970
10971
10972
10973
10974
10975
10976
10977
10978
10979
10980
10981
10982
10983
10984
10985
10986
10987
10988
10989
10990
10991
10992
10993
10994
10995
10996
10997
10998
10999
11000
11001
11002
11003
11004
11005
11006
11007
11008
11009
11010
11011
11012
11013
11014
11015
11016
11017
11018
11019
11020
11021
11022
11023
11024
11025
11026
11027
11028
11029
11030
11031
11032
11033
11034
11035
11036
11037
11038
11039
11040
11041
11042
11043
11044
11045
11046
11047
11048
11049
11050
11051
11052
11053
11054
11055
11056
11057
11058
11059
11060
11061
11062
11063
11064
11065
11066
11067
11068
11069
11070
11071
11072
11073
11074
11075
11076
11077
11078
11079
11080
11081
11082
11083
11084
11085
11086
11087
11088
11089
11090
11091
11092
11093
11094
11095
11096
11097
11098
11099
11100
11101
11102
11103
11104
11105
11106
11107
11108
11109
11110
11111
11112
11113
11114
11115
11116
11117
11118
11119
11120
11121
11122
11123
11124
11125
11126
11127
11128
11129
11130
11131
11132
11133
11134
11135
11136
11137
11138
11139
11140
11141
11142
11143
11144
11145
11146
11147
11148
11149
11150
11151
11152
11153
11154
11155
11156
11157
11158
11159
11160
11161
11162
11163
11164
11165
11166
11167
11168
11169
11170
11171
11172
11173
11174
11175
11176
11177
11178
11179
11180
11181
11182
11183
11184
11185
11186
11187
11188
11189
11190
11191
11192
11193
11194
11195
11196
11197
11198
11199
11200
11201
11202
11203
11204
11205
11206
11207
11208
11209
11210
11211
11212
11213
11214
11215
11216
11217
11218
11219
11220
11221
11222
11223
11224
11225
11226
11227
11228
11229
11230
11231
11232
11233
11234
11235
11236
11237
11238
11239
11240
11241
11242
11243
11244
11245
11246
11247
11248
11249
11250
11251
11252
11253
11254
11255
11256
11257
11258
11259
11260
11261
11262
11263
11264
11265
11266
11267
11268
11269
11270
11271
11272
11273
11274
11275
11276
11277
11278
11279
11280
11281
11282
11283
11284
11285
11286
11287
11288
11289
11290
11291
11292
11293
11294
11295
11296
11297
11298
11299
11300
11301
11302
11303
11304
11305
11306
11307
11308
11309
11310
11311
11312
11313
11314
11315
11316
11317
11318
11319
11320
11321
11322
11323
11324
11325
11326
11327
11328
11329
11330
11331
11332
11333
11334
11335
11336
11337
11338
11339
11340
11341
11342
11343
11344
11345
11346
11347
11348
11349
11350
11351
11352
11353
11354
11355
11356
11357
11358
11359
11360
11361
11362
11363
11364
11365
11366
11367
11368
11369
11370
11371
11372
11373
11374
11375
11376
11377
11378
11379
11380
11381
11382
11383
11384
11385
11386
11387
11388
11389
11390
11391
11392
11393
11394
11395
11396
11397
11398
11399
11400
11401
11402
11403
11404
11405
11406
11407
11408
11409
11410
11411
11412
11413
11414
11415
11416
11417
11418
11419
11420
11421
11422
11423
11424
11425
11426
11427
11428
11429
11430
11431
11432
11433
11434
11435
11436
11437
11438
11439
11440
11441
11442
11443
11444
11445
11446
11447
11448
11449
11450
11451
11452
11453
11454
11455
11456
11457
11458
11459
11460
11461
11462
11463
11464
11465
11466
11467
11468
11469
11470
11471
11472
11473
11474
11475
11476
11477
11478
11479
11480
11481
11482
11483
11484
11485
11486
11487
11488
11489
11490
11491
11492
11493
11494
11495
11496
11497
11498
11499
11500
11501
11502
11503
11504
11505
11506
11507
11508
11509
11510
11511
11512
11513
11514
11515
11516
11517
11518
11519
11520
11521
11522
11523
11524
11525
11526
11527
11528
11529
11530
11531
11532
11533
11534
11535
11536
11537
11538
11539
11540
11541
11542
11543
11544
11545
11546
11547
11548
11549
11550
11551
11552
11553
11554
11555
11556
11557
11558
11559
11560
11561
11562
11563
11564
11565
11566
11567
11568
11569
11570
11571
11572
11573
11574
11575
11576
11577
11578
11579
11580
11581
11582
11583
11584
11585
11586
11587
11588
11589
11590
11591
11592
11593
11594
11595
11596
11597
11598
11599
11600
11601
11602
11603
11604
11605
11606
11607
11608
11609
11610
11611
11612
11613
11614
11615
11616
11617
11618
11619
11620
11621
11622
11623
11624
11625
11626
11627
11628
11629
11630
11631
11632
11633
11634
11635
11636
11637
11638
11639
11640
11641
11642
11643
11644
11645
11646
11647
11648
11649
11650
11651
11652
11653
11654
11655
11656
11657
11658
11659
11660
11661
11662
11663
11664
11665
11666
11667
11668
11669
11670
11671
11672
11673
11674
11675
11676
11677
11678
11679
11680
11681
11682
11683
11684
11685
11686
11687
11688
11689
11690
11691
11692
11693
11694
11695
11696
11697
11698
11699
11700
11701
11702
11703
11704
11705
11706
11707
11708
11709
11710
11711
11712
11713
11714
11715
11716
11717
11718
11719
11720
11721
11722
11723
11724
11725
11726
11727
11728
11729
11730
11731
11732
11733
11734
11735
11736
11737
11738
11739
11740
11741
11742
11743
11744
11745
11746
11747
11748
11749
11750
11751
11752
11753
11754
11755
11756
11757
11758
11759
11760
11761
11762
11763
11764
11765
11766
11767
11768
11769
11770
11771
11772
11773
11774
11775
11776
11777
11778
11779
11780
11781
11782
11783
11784
11785
11786
11787
11788
11789
11790
11791
11792
11793
11794
11795
11796
11797
11798
11799
11800
11801
11802
11803
11804
11805
11806
11807
11808
11809
11810
11811
11812
11813
11814
11815
11816
11817
11818
11819
11820
11821
11822
11823
11824
11825
11826
11827
11828
11829
11830
11831
11832
11833
11834
11835
11836
11837
11838
11839
11840
11841
11842
11843
11844
11845
11846
11847
11848
11849
11850
11851
11852
11853
11854
11855
11856
11857
11858
11859
11860
11861
11862
11863
11864
11865
11866
11867
11868
11869
11870
11871
11872
11873
11874
11875
11876
11877
11878
11879
11880
11881
11882
11883
11884
11885
11886
11887
11888
11889
11890
11891
11892
11893
11894
11895
11896
11897
11898
11899
11900
11901
11902
11903
11904
11905
11906
11907
11908
11909
11910
11911
11912
11913
11914
11915
11916
11917
11918
11919
11920
11921
11922
11923
11924
11925
11926
11927
11928
11929
11930
11931
11932
11933
11934
11935
11936
11937
11938
11939
11940
11941
11942
11943
11944
11945
11946
11947
11948
11949
11950
11951
11952
11953
11954
11955
11956
11957
11958
11959
11960
11961
11962
11963
11964
11965
11966
11967
11968
11969
11970
11971
11972
11973
11974
11975
11976
11977
11978
11979
11980
11981
11982
11983
11984
11985
11986
11987
11988
11989
11990
11991
11992
11993
11994
11995
11996
11997
11998
11999
12000
12001
12002
12003
12004
12005
12006
12007
12008
12009
12010
12011
12012
12013
12014
12015
12016
12017
12018
12019
12020
12021
12022
12023
12024
12025
12026
12027
12028
12029
12030
12031
12032
12033
12034
12035
12036
12037
12038
12039
12040
12041
12042
12043
12044
12045
12046
12047
12048
12049
12050
12051
12052
12053
12054
12055
12056
12057
12058
12059
12060
12061
12062
12063
12064
12065
12066
12067
12068
12069
12070
12071
12072
12073
12074
12075
12076
12077
12078
12079
12080
12081
12082
12083
12084
12085
12086
12087
12088
12089
12090
12091
12092
12093
12094
12095
12096
12097
12098
12099
12100
12101
12102
12103
12104
12105
12106
12107
12108
12109
12110
12111
12112
12113
12114
12115
12116
12117
12118
12119
12120
12121
12122
12123
12124
12125
12126
12127
12128
12129
12130
12131
12132
12133
12134
12135
12136
12137
12138
12139
12140
12141
12142
12143
12144
12145
12146
12147
12148
12149
12150
12151
12152
12153
12154
12155
12156
12157
12158
12159
12160
12161
12162
12163
12164
12165
12166
12167
12168
12169
12170
12171
12172
12173
12174
12175
12176
12177
12178
12179
12180
12181
12182
12183
12184
12185
12186
12187
12188
12189
12190
12191
12192
12193
12194
12195
12196
12197
12198
12199
12200
12201
12202
12203
12204
12205
12206
12207
12208
12209
12210
12211
12212
12213
12214
12215
12216
12217
12218
12219
12220
12221
12222
12223
12224
12225
12226
12227
12228
12229
12230
12231
12232
12233
12234
12235
12236
12237
12238
12239
12240
12241
12242
12243
12244
12245
12246
12247
12248
12249
12250
12251
12252
12253
12254
12255
12256
12257
12258
12259
12260
12261
12262
12263
12264
12265
12266
12267
12268
12269
12270
12271
12272
12273
12274
12275
12276
12277
12278
12279
12280
12281
12282
12283
12284
12285
12286
12287
12288
12289
12290
12291
12292
12293
12294
12295
12296
12297
12298
12299
12300
12301
12302
12303
12304
12305
12306
12307
12308
12309
12310
12311
12312
12313
12314
12315
12316
12317
12318
12319
12320
12321
12322
12323
12324
12325
12326
12327
12328
12329
12330
12331
12332
12333
12334
12335
12336
12337
12338
12339
12340
12341
12342
12343
12344
12345
12346
12347
12348
12349
12350
12351
12352
12353
12354
12355
12356
12357
12358
12359
12360
12361
12362
12363
12364
12365
12366
12367
12368
12369
12370
12371
12372
12373
12374
12375
12376
12377
12378
12379
12380
12381
12382
12383
12384
12385
12386
12387
12388
12389
12390
12391
12392
12393
12394
12395
12396
12397
12398
12399
12400
12401
12402
12403
12404
12405
12406
12407
12408
12409
12410
12411
12412
12413
12414
12415
12416
12417
12418
12419
12420
12421
12422
12423
12424
12425
12426
12427
12428
12429
12430
12431
12432
12433
12434
12435
12436
12437
12438
12439
12440
12441
12442
12443
12444
12445
12446
12447
12448
12449
12450
12451
12452
12453
12454
12455
12456
12457
12458
12459
12460
12461
12462
12463
12464
12465
12466
12467
12468
12469
12470
12471
12472
12473
12474
12475
12476
12477
12478
12479
12480
12481
12482
12483
12484
12485
12486
12487
12488
12489
12490
12491
12492
12493
12494
12495
12496
12497
12498
12499
12500
12501
12502
12503
12504
12505
12506
12507
12508
12509
12510
12511
12512
12513
12514
12515
12516
12517
12518
12519
12520
|
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content=
"HTML Tidy for NetBSD (vers 1st August 2004), see www.w3.org" />
<meta http-equiv="Content-Type" content=
"text/html; charset=us-ascii" />
<title>The pkgsrc guide</title>
<link rel="stylesheet" href="/NetBSD.css" type="text/css" />
<meta name="generator" content=
"DocBook XSL Stylesheets VX.X.X" />
<meta name="description" content=
"Information about using the NetBSD package system (pkgsrc) from both a user view for installing packages as well as from a pkgsrc developers' view for creating new packages." />
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084"
alink="#0000FF">
<div class="book" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h1 class="title"><a name="the-pkgsrc-guide" id=
"the-pkgsrc-guide"></a>The pkgsrc guide</h1>
</div>
<div>
<h2 class="subtitle">Documentation on the NetBSD packages
system</h2>
</div>
<div>
<div class="authorgroup">
<div class="author">
<h3 class="author"><span class=
"firstname">Alistair</span> <span class=
"surname">Crooks</span></h3>
<div class="affiliation">
<div class="address">
<p><code class="email"><<a href=
"mailto:agc@NetBSD.org">agc@NetBSD.org</a>></code></p>
</div>
</div>
</div>
<div class="author">
<h3 class="author"><span class=
"firstname">Hubert</span> <span class=
"surname">Feyrer</span></h3>
<div class="affiliation">
<div class="address">
<p><code class="email"><<a href=
"mailto:hubertf@NetBSD.org">hubertf@NetBSD.org</a>></code></p>
</div>
</div>
</div>
<h3 class="corpauthor">The pkgsrc Developers</h3>
</div>
</div>
<div>
<p class="copyright">Copyright © 1994-2004 The
NetBSD Foundation, Inc</p>
</div>
<div xmlns="http://www.w3.org/TR/xhtml1/transitional">
<p xmlns="" class="pubdate">$NetBSD: pkgsrc.xml,v 1.7
2005/05/24 12:39:00 wiz Exp $</p>
</div>
<div>
<div class="abstract">
<p class="title"><b>Abstract</b></p>
<p>Information about using the NetBSD package system
(pkgsrc) from both a user view for installing packages
as well as from a pkgsrc developers' view for creating
new packages.</p>
</div>
</div>
</div>
<hr />
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="chapter"><a href="#introduction">1.
Introduction</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#introduction-section">1.1.
Introduction</a></span></dt>
<dt><span class="sect1"><a href="#overview">1.2.
Overview</a></span></dt>
<dt><span class="sect1"><a href="#terminology">1.3.
Terminology</a></span></dt>
<dt><span class="sect1"><a href="#typography">1.4.
Typography</a></span></dt>
</dl>
</dd>
<dt><span class="part"><a href="#users-guide">I. The pkgsrc
user's guide</a></span></dt>
<dd>
<dl>
<dt><span class="chapter"><a href="#getting">2. Where
to get pkgsrc</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href="#as-tar-file">2.1.
As tar file</a></span></dt>
<dt><span class="sect1"><a href="#via-sup">2.2. Via
SUP</a></span></dt>
<dt><span class="sect1"><a href="#via-cvs">2.3. Via
CVS</a></span></dt>
</dl>
</dd>
<dt><span class="chapter"><a href="#platforms">3. Using
pkgsrc on systems other than NetBSD</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#bootstrapping-pkgsrc">3.1. Bootstrapping
pkgsrc</a></span></dt>
<dt><span class="sect1"><a href=
"#platform-specific-notes">3.2. Platform specific
notes</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#darwin">3.2.1. Darwin (Mac OS
X)</a></span></dt>
<dt><span class="sect2"><a href=
"#freebsd">3.2.2. FreeBSD</a></span></dt>
<dt><span class="sect2"><a href=
"#interix">3.2.3. Interix</a></span></dt>
<dt><span class="sect2"><a href="#irix">3.2.4.
IRIX</a></span></dt>
<dt><span class="sect2"><a href="#linux">3.2.5.
Linux</a></span></dt>
<dt><span class="sect2"><a href=
"#openbsd">3.2.6. OpenBSD</a></span></dt>
<dt><span class="sect2"><a href=
"#solaris">3.2.7. Solaris</a></span></dt>
</dl>
</dd>
</dl>
</dd>
<dt><span class="chapter"><a href="#using">4. Using
pkgsrc</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#getting-started">4.1. Working with binary
packages</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#where-to-get-binary-packages">4.1.1. Where to
get binary packages</a></span></dt>
<dt><span class="sect2"><a href=
"#how-to-use-binary-packages">4.1.2. How to use
binary packages</a></span></dt>
<dt><span class="sect2"><a href=
"#a-word-of-warning">4.1.3. A word of
warning</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#building-packages-from-source">4.2. Building
packages from source</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#requirements">4.2.1.
Requirements</a></span></dt>
<dt><span class="sect2"><a href=
"#fetching-distfiles">4.2.2. Fetching
distfiles</a></span></dt>
<dt><span class="sect2"><a href=
"#how-to-build-and-install">4.2.3. How to build
and install</a></span></dt>
<dt><span class="sect2"><a href=
"#selecting-the-compiler">4.2.4. Selecting the
compiler</a></span></dt>
</dl>
</dd>
</dl>
</dd>
<dt><span class="chapter"><a href="#binary">5. Creating
binary packages</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#building-a-single-binary-package">5.1. Building a
single binary package</a></span></dt>
<dt><span class="sect1"><a href=
"#settings-for-creationg-of-binary-packages">5.2.
Settings for creation of binary
packages</a></span></dt>
<dt><span class="sect1"><a href="#bulkbuild">5.3.
Doing a bulk build of all packages</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#binary.configuration">5.3.1.
Configuration</a></span></dt>
<dt><span class="sect2"><a href=
"#other-environmental-considerations">5.3.2.
Other environmental
considerations</a></span></dt>
<dt><span class="sect2"><a href=
"#operation">5.3.3. Operation</a></span></dt>
<dt><span class="sect2"><a href=
"#what-it-does">5.3.4. What it
does</a></span></dt>
<dt><span class="sect2"><a href=
"#disk-space-requirements">5.3.5. Disk space
requirements</a></span></dt>
<dt><span class="sect2"><a href=
"#setting-up-a-sandbox">5.3.6. Setting up a
sandbox for chroot'ed builds</a></span></dt>
<dt><span class="sect2"><a href=
"#building-a-partial-set">5.3.7. Building a
partial set of packages</a></span></dt>
<dt><span class="sect2"><a href=
"#bulk-upload">5.3.8. Uploading results of a
bulk build</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#creating-cdroms">5.4. Creating a multiple CD-ROM
packages collection</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#cdpack-example">5.4.1. Example of
cdpack</a></span></dt>
</dl>
</dd>
</dl>
</dd>
<dt><span class="chapter"><a href="#faq">6. Frequently
Asked Questions</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#mailing-list-pointers">6.1. Are there any mailing
lists for pkg-related discussion?</a></span></dt>
<dt><span class="sect1"><a href=
"#pkgviews-docs">6.2. Where's the pkgviews
documentation?</a></span></dt>
<dt><span class="sect1"><a href=
"#faq-pkgtools">6.3. Utilities for package
management (pkgtools)</a></span></dt>
<dt><span class="sect1"><a href=
"#non-root-pkgsrc">6.4. How to use pkgsrc as
non-root</a></span></dt>
<dt><span class="sect1"><a href=
"#resume-transfers">6.5. How to resume transfers
when fetching distfiles?</a></span></dt>
<dt><span class="sect1"><a href=
"#XFree86-from-pkgsrc">6.6. How can I install/use
XFree86 from pkgsrc?</a></span></dt>
<dt><span class="sect1"><a href=
"#x.org-from-pkgsrc">6.7. How can I install/use
X.org from pkgsrc?</a></span></dt>
<dt><span class="sect1"><a href=
"#fetch-behind-firewall">6.8. How to fetch files
from behind a firewall</a></span></dt>
<dt><span class="sect1"><a href="#passive-ftp">6.9.
How do I tell <span><strong class="command">make
fetch</strong></span> to do passive
FTP?</a></span></dt>
<dt><span class="sect1"><a href=
"#fetching-all-distfiles">6.10. How to fetch all
distfiles at once</a></span></dt>
<dt><span class="sect1"><a href=
"#tmac.andoc-missing">6.11. What does
“<span class="quote">Don't know how to make
/usr/share/tmac/tmac.andoc</span>”
mean?</a></span></dt>
<dt><span class="sect1"><a href=
"#bsd.own.mk-missing">6.12. What does
“<span class="quote">Could not find
bsd.own.mk</span>” mean?</a></span></dt>
<dt><span class="sect1"><a href=
"#using-sudo-with-pkgsrc">6.13. Using 'sudo' with
pkgsrc</a></span></dt>
<dt><span class="sect1"><a href="#faq.conf">6.14.
Configuration files handling and
placement</a></span></dt>
<dt><span class="sect1"><a href=
"#audit-packages">6.15. Automated security
checks</a></span></dt>
</dl>
</dd>
</dl>
</dd>
<dt><span class="part"><a href="#developers-guide">II. The
pkgsrc developer's guide</a></span></dt>
<dd>
<dl>
<dt><span class="chapter"><a href="#components">7.
Package components - files, directories and
contents</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#components.Makefile">7.1. <code class=
"filename">Makefile</code></a></span></dt>
<dt><span class="sect1"><a href=
"#components.distinfo">7.2. <code class=
"filename">distinfo</code></a></span></dt>
<dt><span class="sect1"><a href=
"#components.patches">7.3.
patches/*</a></span></dt>
<dt><span class="sect1"><a href=
"#other-mandatory-files">7.4. Other mandatory
files</a></span></dt>
<dt><span class="sect1"><a href=
"#components.optional">7.5. Optional
files</a></span></dt>
<dt><span class="sect1"><a href="#work-dir">7.6.
<code class="filename">work*</code></a></span></dt>
<dt><span class="sect1"><a href="#files-dir">7.7.
<code class=
"filename">files/*</code></a></span></dt>
</dl>
</dd>
<dt><span class="chapter"><a href="#makefile">8.
Programming in <code class=
"filename">Makefile</code>s</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#makefile.variables">8.1. <code class=
"filename">Makefile</code>
variables</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#makefile.variables.names">8.1.1. Naming
conventions</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#makefile.code">8.2. Code snippets</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#adding-to-list">8.2.1. Adding things to a
list</a></span></dt>
<dt><span class="sect2"><a href=
"#converting-internal-to-external">8.2.2.
Converting an internal list into an external
list</a></span></dt>
<dt><span class="sect2"><a href=
"#passing-variable-to-shell">8.2.3. Passing
variables to a shell command</a></span></dt>
<dt><span class="sect2"><a href=
"#quoting-guideline">8.2.4. Quoting
guideline</a></span></dt>
<dt><span class="sect2"><a href=
"#bsd-make-bug-workaround">8.2.5. Workaround
for a bug in BSD Make</a></span></dt>
</dl>
</dd>
</dl>
</dd>
<dt><span class="chapter"><a href="#plist">9. PLIST
issues</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href="#rcs-id">9.1. RCS
ID</a></span></dt>
<dt><span class="sect1"><a href=
"#automatic-plist-generation">9.2. Semi-automatic
<code class="filename">PLIST</code>
generation</a></span></dt>
<dt><span class="sect1"><a href="#print-PLIST">9.3.
Tweaking output of <span><strong class=
"command">make
print-PLIST</strong></span></a></span></dt>
<dt><span class="sect1"><a href="#plist.misc">9.4.
Variable substitution in PLIST</a></span></dt>
<dt><span class="sect1"><a href=
"#manpage-compression">9.5.
Manpage-compression</a></span></dt>
<dt><span class="sect1"><a href=
"#using-PLIST_SRC">9.6. Changing PLIST source with
<code class=
"varname">PLIST_SRC</code></a></span></dt>
<dt><span class="sect1"><a href=
"#platform-specific-plist">9.7. Platform specific
and differing PLISTs</a></span></dt>
<dt><span class="sect1"><a href=
"#faq.common-dirs">9.8. Sharing directories between
packages</a></span></dt>
</dl>
</dd>
<dt><span class="chapter"><a href="#buildlink">10.
Buildlink methodology</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#converting-to-buildlink3">10.1. Converting
packages to use buildlink3</a></span></dt>
<dt><span class="sect1"><a href=
"#creating-buildlink3.mk">10.2. Writing
<code class="filename">buildlink3.mk</code>
files</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#anatomy-of-bl3">10.2.1. Anatomy of a
buildlink3.mk file</a></span></dt>
<dt><span class="sect2"><a href=
"#updating-buildlink-depends">10.2.2. Updating
<code class=
"varname">BUILDLINK_DEPENDS.<em class=
"replaceable"><code>pkg</code></em></code> in
<code class="filename">buildlink3.mk</code>
files</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#writing-builtin.mk">10.3. Writing <code class=
"filename">builtin.mk</code> files</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#anatomy-of-builtin.mk">10.3.1. Anatomy of a
<code class="filename">builtin.mk</code>
file</a></span></dt>
<dt><span class="sect2"><a href=
"#native-or-pkgsrc-preference">10.3.2. Global
preferences for native or pkgsrc
software</a></span></dt>
</dl>
</dd>
</dl>
</dd>
<dt><span class="chapter"><a href="#options">11.
Options handling</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#global-default-options">11.1. Global default
options</a></span></dt>
<dt><span class="sect1"><a href=
"#converting-to-options">11.2. Converting packages
to use <code class=
"filename">bsd.options.mk</code></a></span></dt>
</dl>
</dd>
<dt><span class="chapter"><a href="#build">12. The
build process</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#build.prefix">12.1. Program
location</a></span></dt>
<dt><span class="sect1"><a href=
"#main-targets">12.2. Main targets</a></span></dt>
<dt><span class="sect1"><a href=
"#build.helpful-targets">12.3. Other helpful
targets</a></span></dt>
</dl>
</dd>
<dt><span class="chapter"><a href="#fixes">13. Notes on
fixes for packages</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#general-operation">13.1. General
operation</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#pulling-vars-from-etc-mk.conf">13.1.1. How to
pull in variables from
/etc/mk.conf</a></span></dt>
<dt><span class="sect2"><a href=
"#where-to-install-documentation">13.1.2. Where
to install documentation</a></span></dt>
<dt><span class="sect2"><a href=
"#restricted-packages">13.1.3. Restricted
packages</a></span></dt>
<dt><span class="sect2"><a href=
"#dependencies">13.1.4. Handling
dependencies</a></span></dt>
<dt><span class="sect2"><a href=
"#conflicts">13.1.5. Handling conflicts with
other packages</a></span></dt>
<dt><span class="sect2"><a href=
"#not-building-packages">13.1.6. Packages that
cannot or should not be built</a></span></dt>
<dt><span class="sect2"><a href=
"#undeletable-packages">13.1.7. Packages which
should not be deleted, once
installed</a></span></dt>
<dt><span class="sect2"><a href=
"#security-handling">13.1.8. Handling packages
with security problems</a></span></dt>
<dt><span class="sect2"><a href=
"#compiler-bugs">13.1.9. How to handle compiler
bugs</a></span></dt>
<dt><span class="sect2"><a href=
"#bumping-pkgrevision">13.1.10. How to handle
incrementing versions when fixing an existing
package</a></span></dt>
<dt><span class="sect2"><a href=
"#portability-of-packages">13.1.11. Portability
of packages</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#downloading-issues">13.2. Possible downloading
issues</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#no-plain-download">13.2.1. Packages whose
distfiles aren't available for plain
downloading</a></span></dt>
<dt><span class="sect2"><a href=
"#modified-distfiles-same-name">13.2.2. How to
handle modified distfiles with the 'old'
name</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#configuration-gotchas">13.3. Configuration
gotchas</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#fixes.libtool">13.3.1. Shared libraries -
libtool</a></span></dt>
<dt><span class="sect2"><a href=
"#using-libtool">13.3.2. Using libtool on GNU
packages that already support
libtool</a></span></dt>
<dt><span class="sect2"><a href=
"#autoconf-automake">13.3.3. GNU
Autoconf/Automake</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#building-considerations">13.4. Building
considerations</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#cpp-defines">13.4.1. CPP
defines</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#package-specific-actions">13.5. Package specific
actions</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#package-configuration-files">13.5.1. Package
configuration files</a></span></dt>
<dt><span class="sect2"><a href=
"#user-interaction">13.5.2. User
interaction</a></span></dt>
<dt><span class="sect2"><a href=
"#handling-licenses">13.5.3. Handling
licenses</a></span></dt>
<dt><span class="sect2"><a href=
"#creating-accounts">13.5.4. Creating an
account from a package</a></span></dt>
<dt><span class="sect2"><a href=
"#installing-score-files">13.5.5. Installing
score files</a></span></dt>
<dt><span class="sect2"><a href=
"#login-shells">13.5.6. Packages providing
login shells</a></span></dt>
<dt><span class="sect2"><a href=
"#perl-scripts">13.5.7. Packages containing
perl scripts</a></span></dt>
<dt><span class="sect2"><a href=
"#hardcoded-paths">13.5.8. Packages with
hardcoded paths to other
interpreters</a></span></dt>
<dt><span class="sect2"><a href=
"#perl-modules">13.5.9. Packages installing
perl modules</a></span></dt>
<dt><span class="sect2"><a href=
"#faq.info-files">13.5.10. Packages installing
info files</a></span></dt>
<dt><span class="sect2"><a href=
"#gconf2-data-files">13.5.11. Packages
installing GConf2 data files</a></span></dt>
<dt><span class="sect2"><a href=
"#scrollkeeper-data-files">13.5.12. Packages
installing scrollkeeper data
files</a></span></dt>
<dt><span class="sect2"><a href=
"#x11-fonts">13.5.13. Packages installing X11
fonts</a></span></dt>
<dt><span class="sect2"><a href=
"#gtk2-modules">13.5.14. Packages installing
GTK2 modules</a></span></dt>
<dt><span class="sect2"><a href=
"#sgml-xml-data">13.5.15. Packages installing
SGML or XML data</a></span></dt>
<dt><span class="sect2"><a href=
"#mime-database">13.5.16. Packages installing
extensions to the MIME database</a></span></dt>
<dt><span class="sect2"><a href=
"#intltool">13.5.17. Packages using
intltool</a></span></dt>
<dt><span class="sect2"><a href=
"#startup-scripts">13.5.18. Packages installing
startup scripts</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#feedback-to-author">13.6. Feedback to the
author</a></span></dt>
</dl>
</dd>
<dt><span class="chapter"><a href="#debug">14.
Debugging</a></span></dt>
<dt><span class="chapter"><a href="#submit">15.
Submitting and Committing</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#submitting-your-package">15.1. Submitting your
packages</a></span></dt>
<dt><span class="sect1"><a href=
"#committing-importing">15.2. Committing: Importing
a package into CVS</a></span></dt>
<dt><span class="sect1"><a href=
"#updating-package">15.3. Updating a package to a
newer version</a></span></dt>
<dt><span class="sect1"><a href=
"#moving-package">15.4. Moving a package in
pkgsrc</a></span></dt>
</dl>
</dd>
</dl>
</dd>
<dt><span class="appendix"><a href="#examples">A. A simple
example package: bison</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href="#example-files">A.1.
files</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#example-Makefile">A.1.1. Makefile</a></span></dt>
<dt><span class="sect2"><a href=
"#example-descr">A.1.2. DESCR</a></span></dt>
<dt><span class="sect2"><a href=
"#example-plist">A.1.3. PLIST</a></span></dt>
<dt><span class="sect2"><a href=
"#checking-package-with-pkglint">A.1.4. Checking a
package with <span><strong class=
"command">pkglint</strong></span></a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href="#steps-for-b-i-p">A.2.
Steps for building, installing,
packaging</a></span></dt>
</dl>
</dd>
<dt><span class="appendix"><a href="#logs">B. Build
logs</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href="#logs.building">B.1.
Building figlet</a></span></dt>
<dt><span class="sect1"><a href="#logs.package">B.2.
Packaging figlet</a></span></dt>
</dl>
</dd>
<dt><span class="appendix"><a href="#ftp-layout">C. Layout
of the FTP server's package archive</a></span></dt>
<dt><span class="appendix"><a href="#editing">D. Editing
guidelines for the pkgsrc guide</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href="#targets">D.1.
Targets</a></span></dt>
<dt><span class="sect1"><a href="#procedure">D.2.
Procedure</a></span></dt>
</dl>
</dd>
</dl>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="introduction" id=
"introduction"></a>Chapter 1. Introduction</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href=
"#introduction-section">1.1. Introduction</a></span></dt>
<dt><span class="sect1"><a href="#overview">1.2.
Overview</a></span></dt>
<dt><span class="sect1"><a href="#terminology">1.3.
Terminology</a></span></dt>
<dt><span class="sect1"><a href="#typography">1.4.
Typography</a></span></dt>
</dl>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"introduction-section" id=
"introduction-section"></a>1.1. Introduction</h2>
</div>
</div>
</div>
<p>There is a lot of software freely available for Unix
based systems, which usually runs on NetBSD and other
Unix-flavoured systems, too, sometimes with some
modifications. The NetBSD Packages Collection (pkgsrc)
incorporates any such changes necessary to make that
software run, and makes the installation (and
de-installation) of the software package easy by means of a
single command.</p>
<p>Once the software has been built, it is manipulated with
the <span><strong class="command">pkg_*</strong></span>
tools so that installation and de-installation, printing of
an inventory of all installed packages and retrieval of
one-line comments or more verbose descriptions are all
simple.</p>
<p>pkgsrc currently contains several thousand packages,
including:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/apache/README.html"
class="pkgname">www/apache</a> - The Apache web
server</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/mozilla/README.html"
class="pkgname">www/mozilla</a> - The Mozilla web
browser</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/meta-pkgs/gnome/README.html"
class="pkgname">meta-pkgs/gnome</a> - The GNOME
Desktop Environment</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/meta-pkgs/kde3/README.html"
class="pkgname">meta-pkgs/kde3</a> - The K Desktop
Environment</p>
</li>
</ul>
</div>
<p>...just to name a few.</p>
<p>pkgsrc has built-in support for handling varying
dependencies, such as pthreads and X11, and extended
features such as IPv6 support on a range of platforms.</p>
<p>pkgsrc was derived from FreeBSD's ports system, and
initially developed for NetBSD only. Since then, pkgsrc has
grown a lot, and now supports the following platforms:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><a href="http://developer.apple.com/darwin/"
target="_top">Darwin</a> (<a href=
"http://www.apple.com/macosx/" target="_top">Mac OS
X</a>)</p>
</li>
<li>
<p><a href="http://www.DragonFlyBSD.org/" target=
"_top">DragonFlyBSD</a></p>
</li>
<li>
<p><a href="http://www.FreeBSD.org/" target=
"_top">FreeBSD</a></p>
</li>
<li>
<p>Microsoft Windows, via <a href=
"http://www.microsoft.com/windows/sfu/" target=
"_top">Interix</a></p>
</li>
<li>
<p><a href="http://www.sgi.com/software/irix6.5/"
target="_top">IRIX</a></p>
</li>
<li>
<p><a href="http://www.linux.org/" target=
"_top">Linux</a></p>
</li>
<li>
<p><a href="http://www.NetBSD.org/" target=
"_top">NetBSD</a> (of course)</p>
</li>
<li>
<p><a href="http://h30097.www3.hp.com/" target=
"_top">Tru64</a> (Digital UNIX, OSF1)</p>
</li>
<li>
<p><a href="http://www.openbsd.org/" target=
"_top">OpenBSD</a></p>
</li>
<li>
<p><a href="http://www.sun.com/solaris/" target=
"_top">Solaris</a></p>
</li>
</ul>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"overview" id="overview"></a>1.2. Overview</h2>
</div>
</div>
</div>
<p>This document is divided into two parts. The first,
<a href="#users-guide" title=
"Part I. The pkgsrc user's guide">The pkgsrc
user's guide</a>, describes how one can use one of the
packages in the Package Collection, either by installing a
precompiled binary package, or by building one's own copy
using the NetBSD package system. The second part, <a href=
"#developers-guide" title=
"Part II. The pkgsrc developer's guide">The
pkgsrc developer's guide</a>, explains how to prepare a
package so it can be easily built by other NetBSD users
without knowing about the package's building details.</p>
<p>This document is available in various formats:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><a href="index.html" target="_top">HTML</a></p>
</li>
<li>
<p><a href="pkgsrc.pdf" target="_top">PDF</a></p>
</li>
<li>
<p><a href="pkgsrc.ps" target="_top">PS</a></p>
</li>
<li>
<p><a href="pkgsrc.txt" target="_top">TXT</a></p>
</li>
</ul>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"terminology" id=
"terminology"></a>1.3. Terminology</h2>
</div>
</div>
</div>
<p>There has been a lot of talk about “<span class=
"quote">ports</span>”, “<span class=
"quote">packages</span>”, etc. so far. Here is a
description of all the terminology used within this
document.</p>
<div class="variablelist">
<dl>
<dt><span class="term">Package</span></dt>
<dd>
<p>A set of files and building instructions that
describe what's necessary to build a certain piece of
software using pkgsrc. Packages are traditionally
stored under <code class=
"filename">/usr/pkgsrc</code>.</p>
</dd>
<dt><span class="term">The NetBSD package
system</span></dt>
<dd>
<p>This is the former name of “<span class=
"quote">pkgsrc</span>”. It is part of the
NetBSD operating system and can be bootstrapped to
run on non-NetBSD operating systems as well. It
handles building (compiling), installing, and
removing of packages.</p>
</dd>
<dt><span class="term">Distfile</span></dt>
<dd>
<p>This term describes the file or files that are
provided by the author of the piece of software to
distribute his work. All the changes necessary to
build on NetBSD are reflected in the corresponding
package. Usually the distfile is in the form of a
compressed tar-archive, but other types are possible,
too. Distfiles are usually stored below <code class=
"filename">/usr/pkgsrc/distfiles</code>.</p>
</dd>
<dt><span class="term">Port</span></dt>
<dd>
<p>This is the term used by FreeBSD and OpenBSD
people for what we call a package. In NetBSD
terminology, “<span class=
"quote">port</span>” refers to a different
architecture.</p>
</dd>
<dt><span class="term">Precompiled/binary
package</span></dt>
<dd>
<p>A set of binaries built with pkgsrc from a
distfile and stuffed together in a single
<code class="filename">.tgz</code> file so it can be
installed on machines of the same machine
architecture without the need to recompile. Packages
are usually generated in <code class=
"filename">/usr/pkgsrc/packages</code>; there is also
an archive on <a href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/" target=
"_top">ftp.NetBSD.org</a>.</p>
<p>Sometimes, this is referred to by the term
“<span class="quote">package</span>” too,
especially in the context of precompiled
packages.</p>
</dd>
<dt><span class="term">Program</span></dt>
<dd>
<p>The piece of software to be installed which will
be constructed from all the files in the Distfile by
the actions defined in the corresponding package.</p>
</dd>
</dl>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"typography" id=
"typography"></a>1.4. Typography</h2>
</div>
</div>
</div>
<p>When giving examples for commands, shell prompts are
used to show if the command should/can be issued as root,
or if “<span class="quote">normal</span>” user
privileges are sufficient. We use a <code class=
"prompt">#</code> for root's shell prompt, and a
<code class="prompt">%</code> for users' shell prompt,
assuming they use the C-shell or tcsh.</p>
</div>
</div>
<div class="part" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h1 class="title"><a name="users-guide" id=
"users-guide"></a>The pkgsrc user's guide</h1>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="chapter"><a href="#getting">2. Where to
get pkgsrc</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href="#as-tar-file">2.1.
As tar file</a></span></dt>
<dt><span class="sect1"><a href="#via-sup">2.2. Via
SUP</a></span></dt>
<dt><span class="sect1"><a href="#via-cvs">2.3. Via
CVS</a></span></dt>
</dl>
</dd>
<dt><span class="chapter"><a href="#platforms">3. Using
pkgsrc on systems other than NetBSD</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#bootstrapping-pkgsrc">3.1. Bootstrapping
pkgsrc</a></span></dt>
<dt><span class="sect1"><a href=
"#platform-specific-notes">3.2. Platform specific
notes</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href="#darwin">3.2.1.
Darwin (Mac OS X)</a></span></dt>
<dt><span class="sect2"><a href="#freebsd">3.2.2.
FreeBSD</a></span></dt>
<dt><span class="sect2"><a href="#interix">3.2.3.
Interix</a></span></dt>
<dt><span class="sect2"><a href="#irix">3.2.4.
IRIX</a></span></dt>
<dt><span class="sect2"><a href="#linux">3.2.5.
Linux</a></span></dt>
<dt><span class="sect2"><a href="#openbsd">3.2.6.
OpenBSD</a></span></dt>
<dt><span class="sect2"><a href="#solaris">3.2.7.
Solaris</a></span></dt>
</dl>
</dd>
</dl>
</dd>
<dt><span class="chapter"><a href="#using">4. Using
pkgsrc</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#getting-started">4.1. Working with binary
packages</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#where-to-get-binary-packages">4.1.1. Where to
get binary packages</a></span></dt>
<dt><span class="sect2"><a href=
"#how-to-use-binary-packages">4.1.2. How to use
binary packages</a></span></dt>
<dt><span class="sect2"><a href=
"#a-word-of-warning">4.1.3. A word of
warning</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#building-packages-from-source">4.2. Building
packages from source</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#requirements">4.2.1.
Requirements</a></span></dt>
<dt><span class="sect2"><a href=
"#fetching-distfiles">4.2.2. Fetching
distfiles</a></span></dt>
<dt><span class="sect2"><a href=
"#how-to-build-and-install">4.2.3. How to build
and install</a></span></dt>
<dt><span class="sect2"><a href=
"#selecting-the-compiler">4.2.4. Selecting the
compiler</a></span></dt>
</dl>
</dd>
</dl>
</dd>
<dt><span class="chapter"><a href="#binary">5. Creating
binary packages</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#building-a-single-binary-package">5.1. Building a
single binary package</a></span></dt>
<dt><span class="sect1"><a href=
"#settings-for-creationg-of-binary-packages">5.2.
Settings for creation of binary
packages</a></span></dt>
<dt><span class="sect1"><a href="#bulkbuild">5.3.
Doing a bulk build of all packages</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#binary.configuration">5.3.1.
Configuration</a></span></dt>
<dt><span class="sect2"><a href=
"#other-environmental-considerations">5.3.2.
Other environmental
considerations</a></span></dt>
<dt><span class="sect2"><a href=
"#operation">5.3.3. Operation</a></span></dt>
<dt><span class="sect2"><a href=
"#what-it-does">5.3.4. What it
does</a></span></dt>
<dt><span class="sect2"><a href=
"#disk-space-requirements">5.3.5. Disk space
requirements</a></span></dt>
<dt><span class="sect2"><a href=
"#setting-up-a-sandbox">5.3.6. Setting up a
sandbox for chroot'ed builds</a></span></dt>
<dt><span class="sect2"><a href=
"#building-a-partial-set">5.3.7. Building a
partial set of packages</a></span></dt>
<dt><span class="sect2"><a href=
"#bulk-upload">5.3.8. Uploading results of a bulk
build</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#creating-cdroms">5.4. Creating a multiple CD-ROM
packages collection</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#cdpack-example">5.4.1. Example of
cdpack</a></span></dt>
</dl>
</dd>
</dl>
</dd>
<dt><span class="chapter"><a href="#faq">6. Frequently
Asked Questions</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#mailing-list-pointers">6.1. Are there any mailing
lists for pkg-related discussion?</a></span></dt>
<dt><span class="sect1"><a href="#pkgviews-docs">6.2.
Where's the pkgviews documentation?</a></span></dt>
<dt><span class="sect1"><a href="#faq-pkgtools">6.3.
Utilities for package management
(pkgtools)</a></span></dt>
<dt><span class="sect1"><a href=
"#non-root-pkgsrc">6.4. How to use pkgsrc as
non-root</a></span></dt>
<dt><span class="sect1"><a href=
"#resume-transfers">6.5. How to resume transfers when
fetching distfiles?</a></span></dt>
<dt><span class="sect1"><a href=
"#XFree86-from-pkgsrc">6.6. How can I install/use
XFree86 from pkgsrc?</a></span></dt>
<dt><span class="sect1"><a href=
"#x.org-from-pkgsrc">6.7. How can I install/use X.org
from pkgsrc?</a></span></dt>
<dt><span class="sect1"><a href=
"#fetch-behind-firewall">6.8. How to fetch files from
behind a firewall</a></span></dt>
<dt><span class="sect1"><a href="#passive-ftp">6.9.
How do I tell <span><strong class="command">make
fetch</strong></span> to do passive
FTP?</a></span></dt>
<dt><span class="sect1"><a href=
"#fetching-all-distfiles">6.10. How to fetch all
distfiles at once</a></span></dt>
<dt><span class="sect1"><a href=
"#tmac.andoc-missing">6.11. What does
“<span class="quote">Don't know how to make
/usr/share/tmac/tmac.andoc</span>”
mean?</a></span></dt>
<dt><span class="sect1"><a href=
"#bsd.own.mk-missing">6.12. What does
“<span class="quote">Could not find
bsd.own.mk</span>” mean?</a></span></dt>
<dt><span class="sect1"><a href=
"#using-sudo-with-pkgsrc">6.13. Using 'sudo' with
pkgsrc</a></span></dt>
<dt><span class="sect1"><a href="#faq.conf">6.14.
Configuration files handling and
placement</a></span></dt>
<dt><span class="sect1"><a href=
"#audit-packages">6.15. Automated security
checks</a></span></dt>
</dl>
</dd>
</dl>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="getting" id=
"getting"></a>Chapter 2. Where to get
pkgsrc</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href="#as-tar-file">2.1. As
tar file</a></span></dt>
<dt><span class="sect1"><a href="#via-sup">2.2. Via
SUP</a></span></dt>
<dt><span class="sect1"><a href="#via-cvs">2.3. Via
CVS</a></span></dt>
</dl>
</div>
<p>There are three ways to get pkgsrc. Either as a tar
file, via SUP, or via CVS. All three ways are described
here.</p>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"as-tar-file" id="as-tar-file"></a>2.1. As tar
file</h2>
</div>
</div>
</div>
<p>To get pkgsrc going, you need to get the pkgsrc.tar.gz
file from <a href=
"ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-current/tar_files/pkgsrc.tar.gz"
target="_top">ftp.NetBSD.org</a> and unpack it into
<code class="filename">/usr/pkgsrc</code>.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"via-sup" id="via-sup"></a>2.2. Via SUP</h2>
</div>
</div>
</div>
<p>As an alternative to the tar file, you can get pkgsrc
via the Software Update Protocol, SUP. To do so, make
sure your supfile has a line</p>
<pre class="programlisting">
release=pkgsrc
</pre>
<p>in it, see the examples in <code class=
"filename">/usr/share/examples/supfiles</code>, and that
the <code class="filename">/usr/pkgsrc</code> directory
exists. Then, simply run <span><strong class=
"command">sup -v <em class=
"replaceable"><code>/path/to/your/supfile</code></em></strong></span>.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"via-cvs" id="via-cvs"></a>2.3. Via CVS</h2>
</div>
</div>
</div>
<p>To get pkgsrc via CVS, make sure you have
“<span class="quote">cvs</span>” installed.
To do an initial (full) checkout of pkgsrc, do the
following steps:</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>setenv CVSROOT anoncvs@anoncvs.NetBSD.org:/cvsroot</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>setenv CVS_RSH ssh</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>cd /usr</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>cvs checkout -P pkgsrc</code></strong>
</pre>
<p>This will create the <code class=
"filename">pkgsrc</code> directory in your <code class=
"filename">/usr</code>, and all the package source will
be stored under <code class=
"filename">/usr/pkgsrc</code>. To update pkgsrc after the
initial checkout, make sure you have <code class=
"varname">CVS_RSH</code> set as above, then do:</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>cd /usr/pkgsrc</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>cvs -q update -dP</code></strong>
</pre>
<p>Please also note that it is possible to have multiple
copies of the pkgsrc hierarchy in use at any one time -
all work is done relatively within the pkgsrc tree.</p>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="platforms" id=
"platforms"></a>Chapter 3. Using pkgsrc on
systems other than NetBSD</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href=
"#bootstrapping-pkgsrc">3.1. Bootstrapping
pkgsrc</a></span></dt>
<dt><span class="sect1"><a href=
"#platform-specific-notes">3.2. Platform specific
notes</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href="#darwin">3.2.1.
Darwin (Mac OS X)</a></span></dt>
<dt><span class="sect2"><a href="#freebsd">3.2.2.
FreeBSD</a></span></dt>
<dt><span class="sect2"><a href="#interix">3.2.3.
Interix</a></span></dt>
<dt><span class="sect2"><a href="#irix">3.2.4.
IRIX</a></span></dt>
<dt><span class="sect2"><a href="#linux">3.2.5.
Linux</a></span></dt>
<dt><span class="sect2"><a href="#openbsd">3.2.6.
OpenBSD</a></span></dt>
<dt><span class="sect2"><a href="#solaris">3.2.7.
Solaris</a></span></dt>
</dl>
</dd>
</dl>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"bootstrapping-pkgsrc" id=
"bootstrapping-pkgsrc"></a>3.1. Bootstrapping
pkgsrc</h2>
</div>
</div>
</div>
<p>For operating systems other than NetBSD, we provide a
bootstrap kit to build the required tools to use pkgsrc
on your platform. Besides support for native NetBSD,
pkgsrc and the bootstrap kit have support for the
following operating systems:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>Darwin (Mac OS X)</p>
</li>
<li>
<p>DragonFlyBSD</p>
</li>
<li>
<p>FreeBSD</p>
</li>
<li>
<p>Interix (Windows 2000, XP, 2003)</p>
</li>
<li>
<p>IRIX</p>
</li>
<li>
<p>Linux</p>
</li>
<li>
<p>OpenBSD</p>
</li>
<li>
<p>Solaris</p>
</li>
<li>
<p>Tru64 (Digital UNIX/OSF1)</p>
</li>
</ul>
</div>
<p>Support for other platforms is under development.</p>
<p>Installing the bootstrap kit should be as simple
as:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>env CVS_RSH=ssh cvs -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout pkgsrc</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>cd pkgsrc/bootstrap</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>./bootstrap</code></strong>
</pre>
<p>See <a href="#getting" title=
"Chapter 2. Where to get pkgsrc">Chapter 2,
<i>Where to get pkgsrc</i></a> for other ways to get
pkgsrc before bootstrapping. The given
<span><strong class="command">bootstrap</strong></span>
command will use the defaults of <code class=
"filename">/usr/pkg</code> for the <span class=
"emphasis"><em>prefix</em></span> where programs will be
installed in, and <code class=
"filename">/var/db/pkg</code> for the package database
directory where pkgsrc will do its internal bookkeeping.
However, these can also be set using command-line
arguments.</p>
<p>Binary packages for the pkgsrc tools and an initial
set of packages is available for supported platforms. An
up-to-date list of these can be found on <a href=
"http://www.pkgsrc.org/" target=
"_top">www.pkgsrc.org</a>.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"platform-specific-notes" id=
"platform-specific-notes"></a>3.2. Platform
specific notes</h2>
</div>
</div>
</div>
<p>Here are some platform-specific notes you should be
aware of.</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="darwin" id=
"darwin"></a>3.2.1. Darwin (Mac OS X)</h3>
</div>
</div>
</div>
<p>Darwin 5.x and 6.x are supported. There are two
methods of using pkgsrc on Mac OS X, by using a
<a href="#platform.osx-image" title=
"3.2.1.1. Using a disk image">disk image</a>, or a
<a href="#platform.osx-ufs" title=
"3.2.1.2. Using a UFS partition">UFS
partition</a>.</p>
<p>Before you start, you will need to download and
install the Mac OS X Developer Tools from Apple's
Developer Connection. See <a href=
"http://developer.apple.com/macosx/" target=
"_top">http://developer.apple.com/macosx/</a> for
details. Also, make sure you install X11 for Mac OS X
and the X11 SDK from <a href=
"http://www.apple.com/macosx/x11/download/" target=
"_top">http://www.apple.com/macosx/x11/download/</a> if
you intend to build packages that use the X11 Window
System.</p>
<p>If you already have a UFS partition, or have a spare
partition that you can format as UFS, it is recommended
to use that instead of the disk image. It'll be
somewhat faster and will mount automatically at boot
time, where you must manually mount a disk image.</p>
<div class="note" style=
"margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>You cannot use a HFS+ file system for pkgsrc,
because pkgsrc currently requires the filesystem to
be case-sensitive, and HFS+ is not.</p>
</div>
<div class="sect3" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="platform.osx-image"
id="platform.osx-image"></a>3.2.1.1. Using
a disk image</h4>
</div>
</div>
</div>
<p>Create the disk image:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cd pkgsrc/bootstrap</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>./ufsdiskimage create ~/Documents/NetBSD 512</code></strong> # megabytes - season to taste
<code class="prompt">#</code> <strong class=
"userinput"><code>./ufsdiskimage mount ~/Documents/NetBSD</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>sudo chown `id -u`:`id -g` /Volumes/NetBSD</code></strong>
</pre>
<p>That's it!</p>
</div>
<div class="sect3" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="platform.osx-ufs"
id="platform.osx-ufs"></a>3.2.1.2. Using a
UFS partition</h4>
</div>
</div>
</div>
<p>By default, <code class="filename">/usr</code>
will be on your root file system, normally HFS+. It
is possible to use the default <span class=
"emphasis"><em>prefix</em></span> of <code class=
"filename">/usr/pkg</code> by symlinking <code class=
"filename">/usr/pkg</code> to a directory on a UFS
file system. Obviously, another symlink is required
if you want to place the package database directory
outside the <span class=
"emphasis"><em>prefix</em></span>. e.g.</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>./bootstrap --pkgdbdir /usr/pkg/pkgdb --pkgsrcdir /Volumes/ufs/pkgsrc</code></strong>
</pre>
<p>If you created your partitions at the time of
installing Mac OS X and formatted the target
partition as UFS, it should automatically mount on
<code class="filename">/Volumes/<volume
name></code> when the machine boots. If you are
(re)formatting a partition as UFS, you need to ensure
that the partition map correctly reflects
“<span class="quote">Apple_UFS</span>”
and not “<span class=
"quote">Apple_HFS</span>”.</p>
<p>The problem is that none of the disk tools will
let you touch a disk that is booted from. You can
unmount the partition, but even if you newfs it, the
partition type will be incorrect and the automounter
won't mount it. It can be mounted manually, but it
won't appear in Finder.</p>
<p>You'll need to boot off of the OS X Installation
(User) CD. When the Installation program starts, go
up to the menu and select Disk Utility. Now, you will
be able to select the partition you want to be UFS,
and Format it Apple UFS. Quit the Disk Utility, quit
the installer which will reboot your machine. The new
UFS file system will appear in Finder.</p>
<p>Be aware that the permissions on the new file
system will be writable by root only.</p>
<p>This note is as of 10.2 (Jaguar) and applies to
earlier versions. Hopefully Apple will fix Disk
Utility in 10.3 (Panther).</p>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="freebsd" id=
"freebsd"></a>3.2.2. FreeBSD</h3>
</div>
</div>
</div>
<p>FreeBSD 4.7 and 5.0 have been tested and are
supported, other versions may work.</p>
<p>Care should be taken so that the tools that this kit
installs do not conflict with the FreeBSD userland
tools. There are several steps:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>FreeBSD stores its ports pkg database in
<code class="filename">/var/db/pkg</code>. It is
therefore recommended that you choose a different
location (e.g. <code class=
"filename">/usr/pkgdb</code>) by using the
--pkgdbdir option to the bootstrap script.</p>
</li>
<li>
<p>If you do not intend to use the FreeBSD ports
tools, it's probably a good idea to move them out
of the way to avoid confusion, e.g.</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cd /usr/sbin</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>mv pkg_add pkg_add.orig</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>mv pkg_create pkg_create.orig</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>mv pkg_delete pkg_delete.orig</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>mv pkg_info pkg_info.orig</code></strong>
</pre>
</li>
<li>
<p>An example <code class=
"filename">/etc/mk.conf</code> file will be
placed in <code class=
"filename">/etc/mk.conf.example</code> file when
you use the bootstrap script.</p>
</li>
</ol>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="interix" id=
"interix"></a>3.2.3. Interix</h3>
</div>
</div>
</div>
<p>Interix is a POSIX compatible subsystem for the
Windows NT kernel, providing a Unix-like environment
with a tighter kernel integration than available with
Cygwin. It is part of the Windows Services for Unix
package, available for free for any licensed copy of
Windows 2000, XP (not including XP Home), or 2003. SFU
can be downloaded from <a href=
"http://www.microsoft.com/windows/sfu/" target=
"_top">http://www.microsoft.com/windows/sfu/</a>.</p>
<p>Services for Unix 3.5, current as of this writing,
has been tested. 3.0 or 3.1 may work, but are not
officially supported. (The main difference in 3.0/3.1
is lack of pthreads.)</p>
<div class="sect3" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name=
"platform.interix-sfu-install" id=
"platform.interix-sfu-install"></a>3.2.3.1. When
installing Interix/SFU</h4>
</div>
</div>
</div>
<p>At an absolute minimum, the following packages
must be installed from the Windows Services for Unix
3.5 distribution in order to use pkgsrc:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>Utilities -> Base Utilities</p>
</li>
<li>
<p>Interix GNU Components -> (all)</p>
</li>
<li>
<p>Remote Connectivity</p>
</li>
<li>
<p>Interix SDK</p>
</li>
</ul>
</div>
<p>When using pkgsrc on Interix, DO NOT install the
Utilities subcomponent "UNIX Perl". That is Perl 5.6
without shared module support, installed to
/usr/local, and will only cause confusion. Instead,
install Perl 5.8 from pkgsrc (or from a binary
package).</p>
<p>The Remote Connectivity subcomponent "Windows
Remote Shell Service" does not need to be installed,
but Remote Connectivity itself should be installed in
order to have a working inetd.</p>
<p>Finally, during installation you may be asked
whether to enable setuid behavior for Interix
programs, and whether to make pathnames default to
case-sensitive. Setuid should be enabled, and
case-sensitivity MUST be enabled. (Without
case-sensitivity, a large number of packages
including perl will not build.)</p>
</div>
<div class="sect3" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name=
"platform.interix-sfu-postinstall" id=
"platform.interix-sfu-postinstall"></a>3.2.3.2. What
to do if Interix/SFU is already installed</h4>
</div>
</div>
</div>
<p>If SFU is already installed and you wish to alter
these settings to work with pkgsrc, note the
following things.</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>To uninstall UNIX Perl, use Add/Remove
Programs, select Microsoft Windows Services for
UNIX, then click Change. In the installer,
choose Add or Remove, then uncheck
Utilities->UNIX Perl.</p>
</li>
<li>
<p>To enable case-sensitivity for the
filesystem, run REGEDIT.EXE, and change the
following registry key:</p>
<p>
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\kernel</p>
<p>Set the DWORD value "obcaseinsensitive" to
0; then reboot.</p>
</li>
<li>
<p>To enable setuid binaries (optional), run
REGEDIT.EXE, and change the following registry
key:</p>
<p>
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Services
for UNIX</p>
<p>Set the DWORD value "EnableSetuidBinaries"
to 1; then reboot.</p>
</li>
</ul>
</div>
</div>
<div class="sect3" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name=
"platform.interix-notes" id=
"platform.interix-notes"></a>3.2.3.3. Important
notes for using pkgsrc</h4>
</div>
</div>
</div>
<p>The package imanager (either the pkgsrc "su" user,
or the user running "pkg_add") must be a member of
the local Administrators group. Such a user must also
be used to run the bootstrap. This is slightly
relaxed from the normal pkgsrc requirement of
"root".</p>
<p>The package manager should use a umask of 002.
"make install" will automatically complain if this is
not the case. This ensures that directories written
in /var/db/pkg are Administrators-group
writeable.</p>
<p>The popular Interix binary packages from
http://www.interopsystems.com/ use an older version
of pkgsrc's pkg_* tools. Ideally, these should NOT be
used in conjunction with pkgsrc. If you choose to use
them at the same time as the pkgsrc packages, ensure
that you use the proper pkg_* tools for each type of
binary package.</p>
<p>The TERM setting used for DOS-type console windows
(including those invoked by the csh and ksh startup
shortcuts) is "interix". Most systems don't have a
termcap/terminfo entry for it, but the following
.termcap entry provides adequate emulation in most
cases:</p>
<pre class="programlisting">
interix:kP=\E[S:kN=\E[T:kH=\E[U:dc@:DC@:tc=pcansi:
</pre>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="irix" id=
"irix"></a>3.2.4. IRIX</h3>
</div>
</div>
</div>
<p>You will need a working C compiler, either gcc or
SGI's MIPS and MIPSpro compiler (cc/c89). Please set
the <code class="varname">CC</code> environment
variable according to your preference. If you do not
have a license for the MIPSpro compiler suite, you can
download a gcc tardist file from <a href=
"http://freeware.sgi.com/" target=
"_top">http://freeware.sgi.com/</a>.</p>
<p>Please note that you will need IRIX 6.5.17 or
higher, as this is the earliest version of IRIX
providing support for <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?if_indextoname+3+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">if_indextoname</span>(3)</span></a>,
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?if_nametoindex+3+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">if_nametoindex</span>(3)</span></a>,
etc.</p>
<p>At this point in time, pkgsrc only supports one ABI
at a time. That is, you can not switch between the old
32-bit ABI, the new 32-bit ABI and the 64-bit ABI. If
you start out using "abi=n32", that's what all your
packages will be built with.</p>
<p>Therefore, please make sure that you have no
conflicting <code class="varname">CFLAGS</code> in your
environment or the <code class=
"filename">/etc/mk.conf</code>. Particularly, make sure
that you do not try to link n32 object files with lib64
or vice versa. Check your <code class=
"filename">/etc/compiler.defaults</code>!</p>
<p>If you have the actual pkgsrc tree mounted via NFS
from a different host, please make sure to set
<code class="varname">WRKOBJDIR</code> to a local
directory, as it appears that IRIX linker occasionally
runs into issues when trying to link over a network
mounted filesystem.</p>
<p>The bootstrapping process should set all the right
options for programs such as imake(1), but you may want
to set some options depending on your local setup.
Please see <code class=
"filename">pkgsrc/mk/defaults/mk.conf</code> and, of
course, your compiler's man pages for details.</p>
<p>If you are using SGI's MIPSPro compiler, please
set</p>
<pre class="programlisting">
PKGSRC_COMPILER=mipspro
</pre>
<p>in <code class="filename">/etc/mk.conf</code>.
Otherwise, pkgsrc will assume you are using gcc and may
end up passing invalid flags to the compiler. Note that
bootstrap should create an appropriate <code class=
"filename">mk.conf.example</code> by default.</p>
<p>If you have both the MIPSPro compiler chain
installed as well as gcc, but want to make sure that
MIPRPro is used, please set your <code class=
"varname">PATH</code> to <span class=
"emphasis"><em>not</em></span> include the location of
gcc (often <code class=
"filename">/usr/freeware/bin</code>), and (important)
pass the '--preserve-path' flag.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="linux" id=
"linux"></a>3.2.5. Linux</h3>
</div>
</div>
</div>
<p>Some versions of Linux (for example Debian
GNU/Linux) need either libtermcap or libcurses
(libncurses). Installing the distributions
libncurses-dev package (or equivalent) should fix the
problem.</p>
<p>pkgsrc supports both gcc (GNU Compiler Collection)
and icc (Intel C++ Compiler). gcc is the default. icc
8.0 and 8.1 on i386 have been tested.</p>
<p>To bootstrap using icc, assuming the default icc
installation directory:</p>
<pre class="programlisting">
env CC=/opt/intel_cc_80/bin/icc LDFLAGS=-static-libcxa \
ac_cv___attribute__=yes ./bootstrap
</pre>
<div class="note" style=
"margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>icc 8.1 needs the `-i-static' argument instead of
-static-libcxa.</p>
</div>
<p>icc supports __attribute__, but the GNU configure
test uses a nested function, which icc does not
support. #undef'ing __attribute__ has the unfortunate
side-effect of breaking many of the Linux header files,
which cannot be compiled properly without
__attribute__. The test must be overridden so that
__attribute__ is assumed supported by the compiler.</p>
<p>After bootstrapping, you should set <code class=
"varname">PKGSRC_COMPILER</code> in <code class=
"filename">/etc/mk.conf</code>:</p>
<pre class="programlisting">
PKGSRC_COMPILER=icc
</pre>
<p>The default installation directory for icc is
<code class="filename">/opt/intel_cc_80</code>, which
is also the pkgsrc default. If you have installed it
into a different directory, set <code class=
"varname">ICCBASE</code> in <code class=
"filename">/etc/mk.conf</code>:</p>
<pre class="programlisting">
ICCBASE=/opt/icc
</pre>
<p>pkgsrc uses the static linking method of the runtime
libraries provided by icc, so binaries can be run on
other systems which do not have the shared libraries
installed.</p>
<p>Libtool, however, extracts a list of libraries from
the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?ld+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">ld</span>(1)</span></a> command run
when linking a C++ shared library and records it,
throwing away the -Bstatic and -Bdynamic options
interspersed between the libraries. This means that
libtool-linked C++ shared libraries will have a runtime
dependency on the icc libraries until this is fixed in
libtool.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="openbsd" id=
"openbsd"></a>3.2.6. OpenBSD</h3>
</div>
</div>
</div>
<p>OpenBSD 3.0 and 3.2 are tested and supported.</p>
<p>Care should be taken so that the tools that this kit
installs do not conflict with the OpenBSD userland
tools. There are several steps:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>OpenBSD stores its ports pkg database in
<code class="filename">/var/db/pkg</code>. It is
therefore recommended that you choose a different
location (e.g. <code class=
"filename">/usr/pkgdb</code>) by using the
--pkgdbdir option to the bootstrap script.</p>
</li>
<li>
<p>If you do not intend to use the OpenBSD ports
tools, it's probably a good idea to move them out
of the way to avoid confusion, e.g.</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cd /usr/sbin</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>mv pkg_add pkg_add.orig</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>mv pkg_create pkg_create.orig</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>mv pkg_delete pkg_delete.orig</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>mv pkg_info pkg_info.orig</code></strong>
</pre>
</li>
<li>
<p>An example <code class=
"filename">/etc/mk.conf</code> file will be
placed in <code class=
"filename">/etc/mk.conf.example</code> file when
you use the bootstrap script. OpenBSD's make
program uses <code class=
"filename">/etc/mk.conf</code> as well. You can
work around this by enclosing all the pkgsrc
specific parts of the file with:</p>
<pre class="programlisting">
.ifdef BSD_PKG_MK
# pkgsrc stuff, e.g. insert defaults/mk.conf or similar here
.else
# OpenBSD stuff
.endif
</pre>
</li>
</ol>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="solaris" id=
"solaris"></a>3.2.7. Solaris</h3>
</div>
</div>
</div>
<p>Solaris 2.6 through 9 are supported on both x86 and
sparc. You will need a working C compiler. Both gcc
2.95.3 and Sun WorkShop 5 have been tested.</p>
<p>The following packages are required on Solaris 8 for
the bootstrap process and to build packages.</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>SUNWsprot</p>
</li>
<li>
<p>SUNWarc</p>
</li>
<li>
<p>SUNWbtool</p>
</li>
<li>
<p>SUNWtoo</p>
</li>
<li>
<p>SUNWlibm</p>
</li>
</ul>
</div>
<p>Please note the use of GNU binutils on Solaris is
<span class="emphasis"><em>not</em></span>
supported.</p>
<div class="sect3" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="solaris-gcc-note"
id="solaris-gcc-note"></a>3.2.7.1. If you
are using gcc</h4>
</div>
</div>
</div>
<p>It makes life much simpler if you only use the
same gcc consistently for building all packages.</p>
<p>It is recommended that an external gcc be used
only for bootstrapping, then either build gcc from
<a xmlns="http://www.w3.org/TR/xhtml1/transitional"
href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/lang/gcc/README.html"
class="pkgname">lang/gcc</a> or install a binary gcc
package, then remove gcc used during
bootstrapping.</p>
<p>Binary packages of gcc can be found through
<a href=
"http://www.sun.com/bigadmin/common/freewareSearch.html"
target=
"_top">http://www.sun.com/bigadmin/common/freewareSearch.html</a>.</p>
</div>
<div class="sect3" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name=
"solaris-sun-workshop-note" id=
"solaris-sun-workshop-note"></a>3.2.7.2. If
you are using Sun WorkShop</h4>
</div>
</div>
</div>
<p>You will need at least the following packages
installed (from WorkShop 5.0)</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>SPROcc - Sun WorkShop Compiler C 5.0</p>
</li>
<li>
<p>SPROcpl - Sun WorkShop Compiler C++ 5.0</p>
</li>
<li>
<p>SPROild - Sun WorkShop Incremental
Linker</p>
</li>
<li>
<p>SPROlang - Sun WorkShop Compilers common
components</p>
</li>
</ul>
</div>
<p>You should set <code class="varname">CC</code>,
<code class="varname">CXX</code> and optionally,
<code class="varname">CPP</code> in <code class=
"filename">/etc/mk.conf</code>, eg.</p>
<pre class="programlisting">
CC= cc
CXX= CC
CPP= /usr/ccs/lib/cpp
</pre>
<p>You may also want to build 64-bit binaries,
eg.</p>
<pre class="programlisting">
CFLAGS= -xtarget=ultra -xarch=v9
</pre>
<p>Whichever compiler you use, please ensure the
compiler tools and your $prefix are in your
<code class="varname">PATH</code>. This includes
<code class="filename">/usr/ccs/{bin,lib}</code> and
eg. <code class=
"filename">/usr/pkg/{bin,sbin}</code>.</p>
</div>
</div>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="using" id=
"using"></a>Chapter 4. Using pkgsrc</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href="#getting-started">4.1.
Working with binary packages</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#where-to-get-binary-packages">4.1.1. Where to get
binary packages</a></span></dt>
<dt><span class="sect2"><a href=
"#how-to-use-binary-packages">4.1.2. How to use
binary packages</a></span></dt>
<dt><span class="sect2"><a href=
"#a-word-of-warning">4.1.3. A word of
warning</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#building-packages-from-source">4.2. Building packages
from source</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#requirements">4.2.1. Requirements</a></span></dt>
<dt><span class="sect2"><a href=
"#fetching-distfiles">4.2.2. Fetching
distfiles</a></span></dt>
<dt><span class="sect2"><a href=
"#how-to-build-and-install">4.2.3. How to build and
install</a></span></dt>
<dt><span class="sect2"><a href=
"#selecting-the-compiler">4.2.4. Selecting the
compiler</a></span></dt>
</dl>
</dd>
</dl>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"getting-started" id=
"getting-started"></a>4.1. Working with binary
packages</h2>
</div>
</div>
</div>
<p>This section describes how to find, retrieve and
install a precompiled binary package that someone else
already prepared for your type of machine.</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"where-to-get-binary-packages" id=
"where-to-get-binary-packages"></a>4.1.1. Where
to get binary packages</h3>
</div>
</div>
</div>
<p>Precompiled packages are stored on ftp.NetBSD.org
and its mirrors in the directory <code class=
"filename">/pub/NetBSD/packages/<OSVERSION>/<ARCH>/</code>
for anonymous FTP access. <code class=
"varname">OSVERSION</code> is the NetBSD version
(<span><strong class="command">uname
-r</strong></span>), <code class="varname">ARCH</code>
is the architecture (<span><strong class=
"command">uname -p</strong></span>). In that directory,
there is a subdirectory for each category plus a
subdirectory <code class="filename">All</code> which
includes the actual binaries in <code class=
"filename">.tgz</code> files. The category
subdirectories use symbolic links to those files (this
is the same directory layout as in <code class=
"filename">/usr/pkgsrc/packages</code>).</p>
<p>This same directory layout applies for CDROM
distributions, only that the directory may be rooted
somewhere else, probably somewhere below <code class=
"filename">/cdrom</code>. Please consult your CDROMs
documentation for the exact location.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"how-to-use-binary-packages" id=
"how-to-use-binary-packages"></a>4.1.2. How
to use binary packages</h3>
</div>
</div>
</div>
<p>If you have the files on a CDROM or downloaded them
to your hard disk, you can install them with the
following command (be sure to <span><strong class=
"command">su</strong></span> to root first):</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>pkg_add /path/to/package.tgz</code></strong>
</pre>
<p>If you have FTP access and you don't want to
download the packages via FTP prior to installation,
you can do this automatically by giving
<span><strong class="command">pkg_add</strong></span>
an FTP URL:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>pkg_add ftp://ftp.NetBSD.org/pub/NetBSD/packages/<OSVERSION>/<ARCH>/All/package.tgz</code></strong>
</pre>
<p>Note that any prerequisite packages needed to run
the package in question will be installed, too,
assuming they are present where you install from.</p>
<p>To save some typing, you can set the <code class=
"varname">PKG_PATH</code> environment variable to a
semicolon separated list of paths (including remote
URLs); trailing slashes are not allowed.</p>
<p>Additionally to the <code class=
"filename">All</code> directory there exists a
<code class="filename">vulnerable</code> directory to
which binary packages with known vulnerabilities are
moved, since removing them could cause missing
dependencies. To use these packages, add the
<code class="filename">vulnerable</code> directory to
your <code class="varname">PKG_PATH</code>. However,
you should run <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/audit-packages/README.html"
class="pkgname">security/audit-packages</a> regularly,
and especially after installing new packages, and
verify that the vulnerabilities are acceptable for your
configuration. An example <code class=
"varname">PKG_PATH</code> would be: <code class=
"filename">ftp://ftp.NetBSD.org/pub/NetBSD/packages/<OSVERSION>/<ARCH>/All;ftp://ftp.NetBSD.org/pub/NetBSD/packages/<OSVERSION>/<ARCH>/vulnerable</code>
Please note that semicolon (';') is a shell
meta-character, so you'll probably have to quote
it.</p>
<p>After you've installed packages, be sure to have
<code class="filename">/usr/pkg/bin</code> and
<code class="filename">/usr/pkg/sbin</code> in your
<code class="varname">PATH</code> so you can actually
start the just installed program.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="a-word-of-warning" id=
"a-word-of-warning"></a>4.1.3. A word of
warning</h3>
</div>
</div>
</div>
<p>Please pay very careful attention to the warnings
expressed in the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_add</span>(1)</span></a> manual
page about the inherent dangers of installing binary
packages which you did not create yourself, and the
security holes that can be introduced onto your system
by indiscriminate adding of such files.</p>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"building-packages-from-source" id=
"building-packages-from-source"></a>4.2. Building
packages from source</h2>
</div>
</div>
</div>
<p>This assumes that the package is already in pkgsrc. If
it is not, see <a href="#developers-guide" title=
"Part II. The pkgsrc developer's guide">Part II,
“The pkgsrc developer's guide”</a> for
instructions how to create your own packages.</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="requirements" id=
"requirements"></a>4.2.1. Requirements</h3>
</div>
</div>
</div>
<p>To build packages from source on a NetBSD system the
“<span class="quote">comp</span>” and the
“<span class="quote">text</span>”
distribution sets must be installed. If you want to
build X11 related packages the “<span class=
"quote">xbase</span>” and “<span class=
"quote">xcomp</span>” distribution sets are
required, too.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="fetching-distfiles"
id="fetching-distfiles"></a>4.2.2. Fetching
distfiles</h3>
</div>
</div>
</div>
<p>The first step for building a package is downloading
the distfiles (i.e. the unmodified source). If they
have not yet been downloaded, pkgsrc will fetch them
automatically.</p>
<p>You can overwrite some of the major distribution
sites to fit to sites that are close to your own. Have
a look at <code class=
"filename">pkgsrc/mk/defaults/mk.conf</code> to find
some examples — in particular, look for the
<code class="varname">MASTER_SORT</code>, <code class=
"varname">MASTER_SORT_REGEX</code> and <code class=
"varname">INET_COUNTRY</code> definitions. This may
save some of your bandwidth and time.</p>
<p>You can change these settings either in your shell's
environment, or, if you want to keep the settings, by
editing the <code class="filename">/etc/mk.conf</code>
file, and adding the definitions there.</p>
<p>If you don't have a permanent Internet connection
and you want to know which files to download,
<span><strong class="command">make
fetch-list</strong></span> will tell you what you'll
need. Put these distfiles into <code class=
"filename">/usr/pkgsrc/distfiles</code>.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"how-to-build-and-install" id=
"how-to-build-and-install"></a>4.2.3. How to
build and install</h3>
</div>
</div>
</div>
<p>Assuming that the distfile has been fetched (see
previous section), become root and change into the
relevant directory and running <span><strong class=
"command">make</strong></span>. For example, type</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>cd misc/figlet</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>make</code></strong>
</pre>
<p>at the shell prompt to build the various components
of the package, and</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make install</code></strong>
</pre>
<p>to install the various components into the correct
places on your system. Installing the package on your
system requires you to be root. However, pkgsrc has a
<span class="emphasis"><em>just-in-time-su</em></span>
feature, which allows you to only become root for the
actual installation step</p>
<p>Taking the figlet utility as an example, we can
install it on our system by building as shown in
<a href="#logs" title=
"Appendix B. Build logs">Appendix B, <i>Build
logs</i></a>.</p>
<p>The program is installed under the default root of
the packages tree - <code class=
"filename">/usr/pkg</code>. Should this not conform to
your tastes, set the <code class=
"varname">LOCALBASE</code> variable in your
environment, and it will use that value as the root of
your packages tree. So, to use <code class=
"filename">/usr/local</code>, set <code class=
"varname">LOCALBASE=/usr/local</code> in your
environment. Please note that you should use a
directory which is dedicated to packages and not shared
with other programs (ie, do not try and use
<code class="varname">LOCALBASE=/usr</code>). Also, you
should not try to add any of your own files or
directories (such as <code class=
"filename">src/</code>, <code class=
"filename">obj/</code>, or <code class=
"filename">pkgsrc/</code>) below the <code class=
"varname">LOCALBASE</code> tree. This is to prevent
possible conflicts between programs and other files
installed by the package system and whatever else may
have been installed there.</p>
<p>Some packages look in <code class=
"filename">/etc/mk.conf</code> to alter some
configuration options at build time. Have a look at
<code class=
"filename">pkgsrc/mk/defaults/mk.conf</code> to get an
overview of what will be set there by default.
Environment variables such as <code class=
"varname">LOCALBASE</code> can be set in <code class=
"filename">/etc/mk.conf</code> to save having to
remember to set them each time you want to use
pkgsrc.</p>
<p>Occasionally, people want to “<span class=
"quote">look under the covers</span>” to see what
is going on when a package is building or being
installed. This may be for debugging purposes, or out
of simple curiosity. A number of utility values have
been added to help with this.</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>If you invoke the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">make</span>(1)</span></a> command
with <code class=
"varname">PKG_DEBUG_LEVEL=2</code>, then a huge
amount of information will be displayed. For
example,</p>
<pre class="screen">
<strong class=
"userinput"><code>make patch PKG_DEBUG_LEVEL=2</code></strong>
</pre>
<p>will show all the commands that are invoked,
up to and including the “<span class=
"quote">patch</span>” stage.</p>
</li>
<li>
<p>If you want to know the value of a certain
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">make</span>(1)</span></a>
definition, then the <code class=
"varname">VARNAME</code> definition should be
used, in conjunction with the show-var target.
e.g. to show the expansion of the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">make</span>(1)</span></a>
variable <code class=
"varname">LOCALBASE</code>:</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>make show-var VARNAME=LOCALBASE</code></strong>
/usr/pkg
<code class="prompt">%</code>
</pre>
</li>
</ol>
</div>
<p>If you want to install a binary package that you've
either created yourself (see next section), that you
put into pkgsrc/packages manually or that is located on
a remote FTP server, you can use the "bin-install"
target. This target will install a binary package - if
available - via <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_add</span>(1)</span></a>, else do a
<span><strong class="command">make
package</strong></span>. The list of remote FTP sites
searched is kept in the variable <code class=
"varname">BINPKG_SITES</code>, which defaults to
ftp.NetBSD.org. Any flags that should be added to
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_add</span>(1)</span></a> can be put
into <code class="varname">BIN_INSTALL_FLAGS</code>.
See <code class=
"filename">pkgsrc/mk/defaults/mk.conf</code> for more
details.</p>
<p>A final word of warning: If you setup a system that
has a non-standard setting for <code class=
"varname">LOCALBASE</code>, be sure to set that before
any packages are installed, as you can not use several
directories for the same purpose. Doing so will result
in pkgsrc not being able to properly detect your
installed packages, and fail miserably. Note also that
precompiled binary packages are usually built with the
default <code class="varname">LOCALBASE</code> of
<code class="filename">/usr/pkg</code>, and that you
should <span class="emphasis"><em>not</em></span>
install any if you use a non-standard <code class=
"varname">LOCALBASE</code>.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"selecting-the-compiler" id=
"selecting-the-compiler"></a>4.2.4. Selecting
the compiler</h3>
</div>
</div>
</div>
<p>By default, pkgsrc will use GCC to build packages.
This may be overridden by setting the following
variables in /etc/mk.conf:</p>
<div class="variablelist">
<dl>
<dt><span class="term"><code class=
"varname">PKGSRC_COMPILER</code>:</span></dt>
<dd>
<p>This is a list of values specifying the chain
of compilers to invoke when building packages.
Valid values are:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><code class="varname">distcc</code>:
distributed C/C++ (chainable)</p>
</li>
<li>
<p><code class="varname">ccache</code>:
compiler cache (chainable)</p>
</li>
<li>
<p><code class="varname">gcc</code>: GNU
C/C++ Compiler</p>
</li>
<li>
<p><code class="varname">mipspro</code>:
Silicon Graphics, Inc. MIPSpro
(n32/n64)</p>
</li>
<li>
<p><code class="varname">mipspro</code>:
Silicon Graphics, Inc. MIPSpro (o32)</p>
</li>
<li>
<p><code class="varname">sunpro</code>:
Microsystems, Inc. WorkShip/Forte/Sun ONE
Studio</p>
</li>
</ul>
</div>
<p>The default is “<span class=
"quote"><code class=
"varname">gcc</code></span>”. You can use
<code class="varname">ccache</code> and/or
<code class="varname">distcc</code> with an
appropriate <code class=
"varname">PKGSRC_COMPILER</code> setting, e.g.
“<span class="quote"><code class=
"varname">ccache gcc</code></span>”. This
variable should always be terminated with a value
for a real compiler.</p>
</dd>
<dt><span class="term"><code class=
"varname">GCC_REQD</code>:</span></dt>
<dd>
<p>This specifies the minimum version of GCC to
use when building packages. If the system GCC
doesn't satisfy this requirement, then pkgsrc
will build and install one of the GCC packages to
use instead.</p>
</dd>
</dl>
</div>
</div>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="binary" id=
"binary"></a>Chapter 5. Creating binary
packages</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href=
"#building-a-single-binary-package">5.1. Building a
single binary package</a></span></dt>
<dt><span class="sect1"><a href=
"#settings-for-creationg-of-binary-packages">5.2.
Settings for creation of binary
packages</a></span></dt>
<dt><span class="sect1"><a href="#bulkbuild">5.3. Doing
a bulk build of all packages</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#binary.configuration">5.3.1.
Configuration</a></span></dt>
<dt><span class="sect2"><a href=
"#other-environmental-considerations">5.3.2. Other
environmental considerations</a></span></dt>
<dt><span class="sect2"><a href="#operation">5.3.3.
Operation</a></span></dt>
<dt><span class="sect2"><a href=
"#what-it-does">5.3.4. What it does</a></span></dt>
<dt><span class="sect2"><a href=
"#disk-space-requirements">5.3.5. Disk space
requirements</a></span></dt>
<dt><span class="sect2"><a href=
"#setting-up-a-sandbox">5.3.6. Setting up a sandbox
for chroot'ed builds</a></span></dt>
<dt><span class="sect2"><a href=
"#building-a-partial-set">5.3.7. Building a partial
set of packages</a></span></dt>
<dt><span class="sect2"><a href=
"#bulk-upload">5.3.8. Uploading results of a bulk
build</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href="#creating-cdroms">5.4.
Creating a multiple CD-ROM packages
collection</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#cdpack-example">5.4.1. Example of
cdpack</a></span></dt>
</dl>
</dd>
</dl>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"building-a-single-binary-package" id=
"building-a-single-binary-package"></a>5.1. Building
a single binary package</h2>
</div>
</div>
</div>
<p>Once you have built and installed a package, you can
create a <span class="emphasis"><em>binary
package</em></span> which can be installed on another
system with <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_add</span>(1)</span></a> This saves
having to build the same package on a group of hosts and
wasting CPU time. It also provides a simple means for
others to install your package, should you distribute
it.</p>
<p>To create a binary package, change into the
appropriate directory in pkgsrc, and run
<span><strong class="command">make
package</strong></span>:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cd misc/figlet</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>make package</code></strong>
</pre>
<p>This will build and install your package (if not
already done), and then build a binary package from what
was installed. You can then use the <span><strong class=
"command">pkg_*</strong></span> tools to manipulate it.
Binary packages are created by default in <code class=
"filename">/usr/pkgsrc/packages</code>, in the form of a
gzipped tar file. See <a href="#logs.package" title=
"B.2. Packaging figlet">Section B.2,
“Packaging figlet”</a> for a continuation of
the above <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/misc/figlet/README.html"
class="pkgname">misc/figlet</a> example.</p>
<p>See <a href="#submit" title=
"Chapter 15. Submitting and Committing">Chapter
15, <i>Submitting and Committing</i></a> for information
on how to submit such a binary package.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"settings-for-creationg-of-binary-packages" id=
"settings-for-creationg-of-binary-packages"></a>5.2. Settings
for creation of binary packages</h2>
</div>
</div>
</div>
<p>See <a href="#build.helpful-targets" title=
"12.3. Other helpful targets">Section 12.3,
“Other helpful targets”</a>.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"bulkbuild" id="bulkbuild"></a>5.3. Doing a
bulk build of all packages</h2>
</div>
</div>
</div>
<p>If you want to get a full set of precompiled binary
packages, this section describes how to get them. Beware
that the bulk build will remove all currently installed
packages from your system! Having an FTP server
configured either on the machine doing the bulk builds or
on a nearby NFS server can help to make the packages
available to everyone. See <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?ftpd+8+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">ftpd</span>(8)</span></a> for more
information. If you use a remote NFS server's storage, be
sure to not actually compile on NFS storage, as this
slows things down a lot.</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="binary.configuration"
id=
"binary.configuration"></a>5.3.1. Configuration</h3>
</div>
</div>
</div>
<div class="sect3" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="binary.mk.conf" id=
"binary.mk.conf"></a>5.3.1.1. /etc/mk.conf</h4>
</div>
</div>
</div>
<p>You may want to set variables in <code class=
"filename">/etc/mk.conf</code>. Look at <code class=
"filename">pkgsrc/mk/defaults/mk.conf</code> for
details of the default settings. You will want to
ensure that <code class=
"varname">ACCEPTABLE_LICENSES</code> meet your local
policy. As used in this example, <code class=
"varname">_ACCEPTABLE=yes</code> accepts <span class=
"emphasis"><em>all</em></span> licenses.</p>
<pre class="programlisting">
PACKAGES?= ${_PKGSRCDIR}/packages/${MACHINE_ARCH}
WRKOBJDIR?= /usr/tmp/pkgsrc # build here instead of in pkgsrc
BSDSRCDIR= /usr/src
BSDXSRCDIR= /usr/xsrc # for x11/xservers
OBJHOSTNAME?= yes # use work.`hostname`
FAILOVER_FETCH= yes # insist on the correct checksum
PKG_DEVELOPER?= yes
_ACCEPTABLE= yes
</pre>
</div>
<div class="sect3" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="build.conf" id=
"build.conf"></a>5.3.1.2. <code class=
"filename">build.conf</code></h4>
</div>
</div>
</div>
<p>In <code class="filename">pkgsrc/mk/bulk</code>,
copy <code class="filename">build.conf-example</code>
to <code class="filename">build.conf</code> and edit
it, following the comments in that file. This is the
config file that determines where log files are
generated after the build, where to mail the build
report to, where your pkgsrc tree is located and the
user to which user to <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?su+8+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">su</span>(8)</span></a> to do a
<span><strong class="command">cvs
update</strong></span>.</p>
</div>
<div class="sect3" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="pre-build.local" id=
"pre-build.local"></a>5.3.1.3. <code class="filename">
pre-build.local</code></h4>
</div>
</div>
</div>
<p>It is possible to configure the bulk build to
perform certain site specific tasks at the end of the
pre-build stage. If the file <code class=
"filename">pre-build.local</code> exists in
<code class="filename">/usr/pkgsrc/mk/bulk</code>, it
will be executed (as a <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?sh+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">sh</span>(1)</span></a> script) at
the end of the usual pre-build stage. An example use
of <code class="filename">pre-build.local</code> is
to have the line:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>echo "I do not have enough disk space to build this pig." \
> pkgsrc/misc/openoffice/$BROKENF</code></strong>
</pre>
<p>to prevent the system from trying to build a
particular package which requires nearly 3 GB of disk
space.</p>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"other-environmental-considerations" id=
"other-environmental-considerations"></a>5.3.2. Other
environmental considerations</h3>
</div>
</div>
</div>
<p>As <code class="filename">/usr/pkg</code> will be
completely deleted at the start of bulk builds, make
sure your login shell is placed somewhere else. Either
drop it into <code class=
"filename">/usr/local/bin</code> (and adjust your login
shell in the passwd file), or (re-)install it via
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_add</span>(1)</span></a> from
<code class="filename">/etc/rc.local</code>, so you can
login after a reboot (remember that your current
process won't die if the package is removed, you just
can't start any new instances of the shell any more).
Also, if you use NetBSD earlier than 1.5, or you still
want to use the pkgsrc version of ssh for some reason,
be sure to install ssh before starting it from
<code class="filename">rc.local</code>:</p>
<pre class="programlisting">
( cd /usr/pkgsrc/security/ssh ; make bulk-install )
if [ -f /usr/pkg/etc/rc.d/sshd ]; then
/usr/pkg/etc/rc.d/sshd
fi
</pre>
<p>Not doing so will result in you being not able to
log in via ssh after the bulk build is finished or if
the machine gets rebooted or crashes. You have been
warned! :)</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="operation" id=
"operation"></a>5.3.3. Operation</h3>
</div>
</div>
</div>
<p>Make sure you don't need any of the packages still
installed.</p>
<div class="warning" style=
"margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Warning</h3>
<p>During the bulk build, <span class=
"emphasis"><em>all packages will be
removed!</em></span></p>
</div>
<p>Be sure to remove all other things that might
interfere with builds, like some libs installed in
<code class="filename">/usr/local</code>, etc. then
become root and type:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cd /usr/pkgsrc</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>sh mk/bulk/build</code></strong>
</pre>
<p>If for some reason your last build didn't complete
(power failure, system panic, ...), you can continue it
by running:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>sh mk/bulk/build restart</code></strong>
</pre>
<p>At the end of the bulk build, you will get a summary
via mail, and find build logs in the directory
specified by <code class="varname">FTP</code> in the
<code class="filename">build.conf</code> file.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="what-it-does" id=
"what-it-does"></a>5.3.4. What it does</h3>
</div>
</div>
</div>
<p>The bulk builds consist of three steps:</p>
<div class="variablelist">
<dl>
<dt><span class="term">1. pre-build</span></dt>
<dd>
<p>The script updates your pkgsrc tree via
(anon)cvs, then cleans out any broken distfiles,
and removes all packages installed.</p>
</dd>
<dt><span class="term">2. the bulk
build</span></dt>
<dd>
<p>This is basically “<span class=
"quote">make bulk-package</span>” with an
optimised order in which packages will be built.
Packages that don't require other packages will
be built first, and packages with many
dependencies will be built later.</p>
</dd>
<dt><span class="term">3. post-build</span></dt>
<dd>
<p>Generates a report that's placed in the
directory specified in the <code class=
"filename">build.conf</code> file named
<code class="filename">broken.html</code>, a
short version of that report will also be mailed
to the build's admin.</p>
</dd>
</dl>
</div>
<p>During the build, a list of broken packages will be
compiled in <code class=
"filename">/usr/pkgsrc/.broken</code> (or <code class=
"filename">.../.broken.${MACHINE}</code> if
<code class="varname">OBJMACHINE</code> is set),
individual build logs of broken builds can be found in
the package's directory. These files are used by the
bulk-targets to mark broken builds to not waste time
trying to rebuild them, and they can be used to debug
these broken package builds later.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"disk-space-requirements" id=
"disk-space-requirements"></a>5.3.5. Disk
space requirements</h3>
</div>
</div>
</div>
<p>Currently, roughly the following requirements are
valid for NetBSD 2.0/i386:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>10 GB - distfiles (NFS ok)</p>
</li>
<li>
<p>8 GB - full set of all binaries (NFS ok)</p>
</li>
<li>
<p>5 GB - temp space for compiling (local disk
recommended)</p>
</li>
</ul>
</div>
<p>Note that all pkgs will be de-installed as soon as
they are turned into a binary package, and that sources
are removed, so there is no excessively huge demand to
disk space. Afterwards, if the package is needed again,
it will be installed via <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_add</span>(1)</span></a> instead of
building again, so there are no cycles wasted by
recompiling.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="setting-up-a-sandbox"
id="setting-up-a-sandbox"></a>5.3.6. Setting
up a sandbox for chroot'ed builds</h3>
</div>
</div>
</div>
<p>If you don't want all the packages nuked from a
machine (rendering it useless for anything but pkg
compiling), there is the possibility of doing the
package bulk build inside a chroot environment.</p>
<p>The first step is to set up a chroot sandbox, e.g.
<code class="filename">/usr/sandbox</code>. This can be
done by using null mounts, or manually.</p>
<p>There is a shell script called <code class=
"filename">pkgsrc/mk/bulk/mksandbox</code> which will
set up the sandbox environment using null mounts. It
will also create a script called <code class=
"filename">sandbox</code> in the root of the sandbox
environment, which will allow the null mounts to be
activated using the <span><strong class=
"command">sandbox mount</strong></span> command and
deactivated using the <span><strong class=
"command">sandbox umount</strong></span> command.</p>
<p>To set up a sandbox environment by hand, after
extracting all the sets from a NetBSD installation or
doing a <span><strong class="command">make distribution
DESTDIR=/usr/sandbox</strong></span> in <code class=
"filename">/usr/src/etc</code>, be sure the following
items are present and properly configured:</p>
<div class="procedure">
<ol type="1">
<li>
<p>Kernel</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cp /netbsd /usr/sandbox</code></strong>
</pre>
</li>
<li>
<p><code class="filename">/dev/*</code></p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cd /usr/sandbox/dev ; sh MAKEDEV all</code></strong>
</pre>
</li>
<li>
<p><code class="filename">/etc/resolv.conf</code>
(for <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/smtpd/README.html"
class="pkgname">security/smtpd</a> and mail):</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cp /etc/resolv.conf /usr/sandbox/etc</code></strong>
</pre>
</li>
<li>
<p>Working(!) mail config (hostname,
sendmail.cf):</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cp /etc/mail/sendmail.cf /usr/sandbox/etc/mail</code></strong>
</pre>
</li>
<li>
<p><code class="filename">/etc/localtime</code>
(for <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/smtpd/README.html"
class="pkgname">security/smtpd</a>):</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>ln -sf /usr/share/zoneinfo/UTC /usr/sandbox/etc/localtime</code></strong>
</pre>
</li>
<li>
<p><code class="filename">/usr/src</code> (system
sources, for <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/sysutils/aperture/README.html"
class="pkgname">sysutils/aperture</a>, <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/net/ppp-mppe/README.html"
class="pkgname">net/ppp-mppe</a>):</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>ln -s ../disk1/cvs .</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>ln -s cvs/src-2.0 src</code></strong>
</pre>
</li>
<li>
<p>Create <code class=
"filename">/var/db/pkg</code> (not part of
default install):</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>mkdir /usr/sandbox/var/db/pkg</code></strong>
</pre>
</li>
<li>
<p>Create <code class="filename">/usr/pkg</code>
(not part of default install):</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>mkdir /usr/sandbox/usr/pkg</code></strong>
</pre>
</li>
<li>
<p>Checkout pkgsrc via cvs into <code class=
"filename">/usr/sandbox/usr/pkgsrc</code>:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cd /usr/sandbox/usr</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>cvs -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -d -P pkgsrc</code></strong>
</pre>
<p>Do not mount/link this to the copy of your
pkgsrc tree you do development in, as this will
likely cause problems!</p>
</li>
<li>
<p>Make <code class=
"filename">/usr/sandbox/usr/pkgsrc/packages</code>
and <code class="filename">.../distfiles</code>
point somewhere appropriate. NFS- and/or
nullfs-mounts may come in handy!</p>
</li>
<li>
<p>Edit <code class=
"filename">/etc/mk.conf</code>, see <a href=
"#binary.mk.conf" title=
"5.3.1.1. /etc/mk.conf">Section 5.3.1.1,
“/etc/mk.conf”</a>.</p>
</li>
<li>
<p>Adjust <code class=
"filename">mk/bulk/build.conf</code> to suit your
needs.</p>
</li>
<li>
<p>If you have set <code class=
"varname">CVS_USER</code> in <code class=
"filename">build.conf</code>, make sure that
account exists and can do a <span><strong class=
"command">cvs ${CVS_FLAGS} update</strong></span>
properly!</p>
</li>
</ol>
</div>
<p>When the chroot sandbox is setup, you can start the
build with the following steps:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cd /usr/sandbox/usr/pkgsrc</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>sh mk/bulk/do-sandbox-build</code></strong>
</pre>
<p>This will just jump inside the sandbox and start
building. At the end of the build, mail will be sent
with the results of the build. Created binary pkgs will
be in <code class=
"filename">/usr/sandbox/usr/pkgsrc/packages</code>
(wherever that points/mounts to/from).</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"building-a-partial-set" id=
"building-a-partial-set"></a>5.3.7. Building
a partial set of packages</h3>
</div>
</div>
</div>
<p>In addition to building a complete set of all
packages in pkgsrc, the <code class=
"filename">pkgsrc/mk/bulk/build</code> script may be
used to build a subset of the packages contained in
pkgsrc. By setting defining <code class=
"varname">SPECIFIC_PKGS</code> in <code class=
"filename">/etc/mk.conf</code>, the variables</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>SITE_SPECIFIC_PKGS</p>
</li>
<li>
<p>HOST_SPECIFIC_PKGS</p>
</li>
<li>
<p>GROUP_SPECIFIC_PKGS</p>
</li>
<li>
<p>USER_SPECIFIC_PKGS</p>
</li>
</ul>
</div>
<p>will define the set of packages which should be
built. The bulk build code will also include any
packages which are needed as dependencies for the
explicitly listed packages.</p>
<p>One use of this is to do a bulk build with
<code class="varname">SPECIFIC_PKGS</code> in a chroot
sandbox periodically to have a complete set of the
binary packages needed for your site available without
the overhead of building extra packages that are not
needed.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="bulk-upload" id=
"bulk-upload"></a>5.3.8. Uploading results
of a bulk build</h3>
</div>
</div>
</div>
<p>This section describes how pkgsrc developers can
upload binary pkgs built by bulk builds to
ftp.NetBSD.org.</p>
<p>If you would like to automatically create checksum
files for the binary packages you intend to upload,
remember to set <code class="varname">MKSUMS=yes</code>
in your <code class=
"filename">mk/bulk/build.conf</code>.</p>
<p>If you would like to PGP sign the checksum files
(highly recommended!), remember to set <code class=
"varname">SIGN_AS=username@NetBSD.org</code> in your
<code class="filename">mk/bulk/build.conf</code>. This
will prompt you for your GPG password to sign the files
before uploading everything.</p>
<p>Then, make sure that you have <code class=
"varname">RSYNC_DST</code> set properly in your
<code class="filename">mk/bulk/build.conf</code> file,
i.e. adjust it to something like one of the
following:</p>
<pre class="screen">
RSYNC_DST=$CVS_USER@ftp.NetBSD.org:/pub/NetBSD/packages/pkgsrc-200xQy/NetBSD-a.b.c/arch/upload
</pre>
<p>Please use appropviate values for "pkgsrc-200xQy",
"NetBSD-a.b.c" and "arch" here. If your login on
ftp.NetBSD.org is different from <code class=
"varname">CVS_USER</code>, write your login directly
into the variable, e.g. my local account is "feyrer",
but for my login "hubertf", I use:</p>
<pre class="screen">
RSYNC_DST=hubertf@ftp.NetBSD.org:/pub/NetBSD/packages/pkgsrc-200xQy/NetBSD-a.b.c/arch/upload
</pre>
<p>A separate <code class="filename">upload</code>
directory is used here to allow "closing" the directory
during upload. To do so, run the following command on
ftp.NetBSD.org next:</p>
<pre class="screen">
nbftp% <strong class=
"userinput"><code>mkdir -p -m 750 /pub/NetBSD/packages/pkgsrc-200xQy/NetBSD-a.b.c/arch/upload</code></strong>
</pre>
<p>Please note that <code class=
"filename">/pub/NetBSD/packages</code> is only
appropriate for packages for the NetBSD operating
system. Binary packages for other operating systems
should go into <code class=
"filename">/pub/pkgsrc</code>.</p>
<p>Before uploading the binary pkgs, ssh authentication
needs to be set up. This example shows how to setup
temporary keys for the root account <span class=
"emphasis"><em>inside the sandbox</em></span> (assuming
that no keys should be present there usually):</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>chroot /usr/sandbox</code></strong>
chroot-<code class="prompt">#</code> <strong class=
"userinput"><code>rm $HOME/.ssh/id-dsa*</code></strong>
chroot-<code class="prompt">#</code> <strong class=
"userinput"><code>ssh-keygen -t dsa</code></strong>
chroot-<code class="prompt">#</code> <strong class=
"userinput"><code>cat $HOME/.ssh/id-dsa.pub</code></strong>
</pre>
<p>Now take the output of <code class=
"filename">id-dsa.pub</code> and append it to your
<code class="filename">~/.ssh/authorized_keys</code>
file on ftp.NetBSD.org. You can remove the key after
the upload is done!</p>
<p>Next, test if your ssh connection really works:</p>
<pre class="screen">
chroot-<code class="prompt">#</code> <strong class=
"userinput"><code>ssh ftp.NetBSD.org date</code></strong>
</pre>
<p>Use "-l yourNetBSDlogin" here as appropriate!</p>
<p>Now after all this works, you can exit the sandbox
and start the upload:</p>
<pre class="screen">
chroot-<code class="prompt">#</code> <strong class=
"userinput"><code>exit</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>cd /usr/sandbox/usr/pkgsrc</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>sh mk/bulk/do-sandbox-upload</code></strong>
</pre>
<p>The upload process may take quite some time. Use
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?ls+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">ls</span>(1)</span></a> or <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?du+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">du</span>(1)</span></a> on the FTP
server to monitor progress of the upload. The upload
script will take care of not uploading restricted
packages and putting vulnerable packages into the
<code class="filename">vulnerable</code>
subdirectory.</p>
<p>After the upload has ended, first thing is to revoke
ssh access:</p>
<pre class="screen">
nbftp% <strong class=
"userinput"><code>vi ~/.ssh/authorized_keys</code></strong>
Gdd:x!
</pre>
<p>Use whatever is needed to remove the key you've
entered before! Last, move the uploaded packages out of
the <code class="filename">upload</code> directory to
have them accessible to everyone:</p>
<pre class="screen">
nbftp% <strong class=
"userinput"><code>cd /pub/NetBSD/packages/pkgsrc-200xQy/NetBSD-a.b.c/arch</code></strong>
nbftp% <strong class=
"userinput"><code>mv upload/* .</code></strong>
nbftp% <strong class="userinput"><code>rmdir upload</code></strong>
nbftp% <strong class="userinput"><code>chmod 755 .</code></strong>
</pre>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"creating-cdroms" id=
"creating-cdroms"></a>5.4. Creating a multiple
CD-ROM packages collection</h2>
</div>
</div>
</div>
<p>After your pkgsrc bulk-build has completed, you may
wish to create a CD-ROM set of the resulting binary
packages to assist in installing packages on other
machines. The <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/cdpack/README.html"
class="pkgname">pkgtools/cdpack</a> package provides a
simple tool for creating the ISO 9660 images.
<span><strong class="command">cdpack</strong></span>
arranges the packages on the CD-ROMs in a way that keeps
all the dependencies for given package on the same CD as
that package.</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="cdpack-example" id=
"cdpack-example"></a>5.4.1. Example of
cdpack</h3>
</div>
</div>
</div>
<p>Complete documentation for cdpack is found in the
cdpack(1) manpage. The following short example assumes
that the binary packages are left in <code class=
"filename">/usr/pkgsrc/packages/All</code> and that
sufficient disk space exists in <code class=
"filename">/u2</code> to hold the ISO 9660 images.</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>mkdir /u2/images</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>pkg_add /usr/pkgsrc/packages/All/cdpack</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>cdpack /usr/pkgsrc/packages/All /u2/images</code></strong>
</pre>
<p>If you wish to include a common set of files
(<code class="filename">COPYRIGHT</code>, <code class=
"filename">README</code>, etc.) on each CD in the
collection, then you need to create a directory which
contains these files. e.g.</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>mkdir /tmp/common</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>echo "This is a README" > /tmp/common/README</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>echo "Another file" > /tmp/common/COPYING</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>mkdir /tmp/common/bin</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>echo "#!/bin/sh" > /tmp/common/bin/myscript</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>echo "echo Hello world" >> /tmp/common/bin/myscript</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>chmod 755 /tmp/common/bin/myscript</code></strong>
</pre>
<p>Now create the images:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cdpack -x /tmp/common /usr/pkgsrc/packages/All /u2/images</code></strong>
</pre>
<p>Each image will contain <code class=
"filename">README</code>, <code class=
"filename">COPYING</code>, and <code class=
"filename">bin/myscript</code> in their root
directories.</p>
</div>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="faq" id=
"faq"></a>Chapter 6. Frequently Asked
Questions</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href=
"#mailing-list-pointers">6.1. Are there any mailing
lists for pkg-related discussion?</a></span></dt>
<dt><span class="sect1"><a href="#pkgviews-docs">6.2.
Where's the pkgviews documentation?</a></span></dt>
<dt><span class="sect1"><a href="#faq-pkgtools">6.3.
Utilities for package management
(pkgtools)</a></span></dt>
<dt><span class="sect1"><a href="#non-root-pkgsrc">6.4.
How to use pkgsrc as non-root</a></span></dt>
<dt><span class="sect1"><a href=
"#resume-transfers">6.5. How to resume transfers when
fetching distfiles?</a></span></dt>
<dt><span class="sect1"><a href=
"#XFree86-from-pkgsrc">6.6. How can I install/use
XFree86 from pkgsrc?</a></span></dt>
<dt><span class="sect1"><a href=
"#x.org-from-pkgsrc">6.7. How can I install/use X.org
from pkgsrc?</a></span></dt>
<dt><span class="sect1"><a href=
"#fetch-behind-firewall">6.8. How to fetch files from
behind a firewall</a></span></dt>
<dt><span class="sect1"><a href="#passive-ftp">6.9. How
do I tell <span><strong class="command">make
fetch</strong></span> to do passive
FTP?</a></span></dt>
<dt><span class="sect1"><a href=
"#fetching-all-distfiles">6.10. How to fetch all
distfiles at once</a></span></dt>
<dt><span class="sect1"><a href=
"#tmac.andoc-missing">6.11. What does
“<span class="quote">Don't know how to make
/usr/share/tmac/tmac.andoc</span>”
mean?</a></span></dt>
<dt><span class="sect1"><a href=
"#bsd.own.mk-missing">6.12. What does
“<span class="quote">Could not find
bsd.own.mk</span>” mean?</a></span></dt>
<dt><span class="sect1"><a href=
"#using-sudo-with-pkgsrc">6.13. Using 'sudo' with
pkgsrc</a></span></dt>
<dt><span class="sect1"><a href="#faq.conf">6.14.
Configuration files handling and
placement</a></span></dt>
<dt><span class="sect1"><a href="#audit-packages">6.15.
Automated security checks</a></span></dt>
</dl>
</div>
<p>This section contains hints, tips & tricks on
special things in pkgsrc that we didn't find a better place
for in the previous chapters, and it contains items for
both pkgsrc users and developers.</p>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"mailing-list-pointers" id=
"mailing-list-pointers"></a>6.1. Are there any
mailing lists for pkg-related discussion?</h2>
</div>
</div>
</div>
<p>The following mailing lists may be of interest to
pkgsrc users:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><a href=
"http://www.NetBSD.org/MailingLists/index.html#pkgsrc-bugs"
target="_top">pkgsrc-bugs</a> -- a list where
problem reports related to pkgsrc are sent and
discussed</p>
</li>
<li>
<p><a href=
"http://www.NetBSD.org/MailingLists/index.html#pkgsrc-bulk"
target="_top">pkgsrc-bulk</a> -- a list where the
results of pkgsrc bulk builds are sent and
discussed</p>
</li>
<li>
<p><a href=
"http://www.NetBSD.org/MailingLists/index.html#pkgsrc-changes"
target="_top">pkgsrc-changes</a> -- a list where
all commit messages to pkgsrc are sent</p>
</li>
<li>
<p><a href=
"http://www.NetBSD.org/MailingLists/index.html#tech-pkg"
target="_top">tech-pkg</a> -- a general discussion
list for all things related to pkgsrc</p>
</li>
</ul>
</div>
<p>To subscribe, do:</p>
<pre class="programlisting">
<code class="prompt">%</code> echo subscribe <em class=
"replaceable"><code>listname</code></em> | mail majordomo@NetBSD.org
</pre>
<p>Archives for all these mailing lists are available
from <a href="http://mail-index.NetBSD.org/" target=
"_top">http://mail-index.NetBSD.org/</a>.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"pkgviews-docs" id=
"pkgviews-docs"></a>6.2. Where's the pkgviews
documentation?</h2>
</div>
</div>
</div>
<p>Pkgviews is tightly integrated with buildlink. You can
find a pkgviews User's guide in <code class=
"filename">pkgsrc/mk/buildlink3/PKGVIEWS_UG</code>.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"faq-pkgtools" id=
"faq-pkgtools"></a>6.3. Utilities for package
management (pkgtools)</h2>
</div>
</div>
</div>
<p>The <code class="filename">pkgsrc/pkgtools</code>
directory pkgtools contains a number of useful utilities
for both users and developers of pkgsrc. This section
attempts only to make the reader aware of the utilities
and when they might be useful, and not to duplicate the
documentation that comes with each package.</p>
<p>Utilities used by pkgsrc (automatically installed when
needed):</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/x11-links/README.html"
class="pkgname">pkgtools/x11-links</a>: symlinks
for use by buildlink</p>
</li>
</ul>
</div>
<p>OS tool augmentation (automatically installed when
needed):</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/digest/README.html"
class="pkgname">pkgtools/digest</a>: calculates
various kinds of checksums (including SHA1)</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/libnbcompat/README.html"
class="pkgname">pkgtools/libnbcompat</a>:
compatibility library for pkgsrc tools</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/mtree/README.html"
class="pkgname">pkgtools/mtree</a>: installed on
non-BSD systems due to lack of native mtree</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_install/README.html"
class="pkgname">pkgtools/pkg_install</a>:
up-to-date replacement for /usr/sbin/pkg_install,
or for use on operating systems where pkg_install
is not present</p>
</li>
</ul>
</div>
<p>Utilities used by pkgsrc (not automatically
installed):</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_tarup/README.html"
class="pkgname">pkgtools/pkg_tarup</a>: create a
binary package from an already-installed package.
used by <span><strong class="command">make
replace</strong></span> to save the old package</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/dfdisk/README.html"
class="pkgname">pkgtools/dfdisk</a>: adds extra
functionality to pkgsrc, allowing it to fetch
distfiles from multiple locations. It currently
supports the following methods: multiple CD-ROMs
and network FTP/HTTP connections.</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/xpkgwedge/README.html"
class="pkgname">pkgtools/xpkgwedge</a>: put X11
packages someplace else (enabled by default)</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/cpuflags/README.html"
class="pkgname">devel/cpuflags</a>: will determine
the best compiler flags to optimise code for your
current CPU and compiler.</p>
</li>
</ul>
</div>
<p>Utilities for keeping track of installed packages,
being up to date, etc:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_chk/README.html"
class="pkgname">pkgtools/pkg_chk</a>: reports on
packages whose installed versions do not match the
latest pkgsrc entries</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdep/README.html"
class="pkgname">pkgtools/pkgdep</a>: makes
dependency graphs of packages, to aid in choosing a
strategy for updating</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdepgraph/README.html"
class="pkgname">pkgtools/pkgdepgraph</a>: makes
graphs from the output of <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdep/README.html"
class="pkgname">pkgtools/pkgdep</a> (uses
graphviz)</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkglint/README.html"
class="pkgname">pkgtools/pkglint</a>: the
pkglint(1) program checks a pkgsrc entry for
errors, lintpkgsrc(1) does various checks on the
complete pkgsrc system.</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgsurvey/README.html"
class="pkgname">pkgtools/pkgsurvey</a>: report what
packages you have installed</p>
</li>
</ul>
</div>
<p>Utilities for people maintaining or creating
individual packages:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdiff/README.html"
class="pkgname">pkgtools/pkgdiff</a>: automate
making and maintaining patches for a package
(includes pkgdiff, pkgvi, mkpatches, ...)</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/rpm2pkg/README.html"
class="pkgname">pkgtools/rpm2pkg</a>, <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/url2pkg/README.html"
class="pkgname">pkgtools/url2pkg</a>: aids in
converting to pkgsrc</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/gensolpkg/README.html"
class="pkgname">pkgtools/gensolpkg</a>: convert
pkgsrc to a Solaris package</p>
</li>
</ul>
</div>
<p>Utilities for people maintaining pkgsrc (or more
obscure pkg utilities)</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgconflict/README.html"
class="pkgname">pkgtools/pkgconflict</a>: find
packages that conflict but aren't marked as
such</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_comp/README.html"
class="pkgname">pkgtools/pkg_comp</a>: build
packages in a chrooted area</p>
</li>
<li>
<p><a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/libkver/README.html"
class="pkgname">pkgtools/libkver</a>: spoof kernel
version for chrooted cross builds</p>
</li>
</ul>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"non-root-pkgsrc" id=
"non-root-pkgsrc"></a>6.4. How to use pkgsrc
as non-root</h2>
</div>
</div>
</div>
<p>If you want to use pkgsrc as non-root user, you can
set some variables to make pkgsrc work under these
conditions. Please see <a href=
"http://mail-index.NetBSD.org/tech-pkg/2003/09/27/0023.html"
target="_top">this message</a> for more details.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"resume-transfers" id=
"resume-transfers"></a>6.5. How to resume
transfers when fetching distfiles?</h2>
</div>
</div>
</div>
<p>By default resuming transfers in pkgsrc is disabled,
but you can enable this feature by adding the option
<code class="varname">PKG_RESUME_TRANSFERS=YES</code>
into <code class="filename">/etc/mk.conf</code>. If,
during a fetch step, an incomplete distfile is found,
pkgsrc will try to resume it.</p>
<p>You can also use a different program than the default
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?ftp+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">ftp</span>(1)</span></a> by changing the
<code class="varname">FETCH_CMD</code> variable. Don't
forget to set <code class=
"varname">FETCH_RESUME_ARGS</code> and <code class=
"varname">FETCH_OUTPUT_ARGS</code> if you are not using
default values.</p>
<p>For example, if you want to use <code class=
"filename">wget</code> to resume downloads, you'll have
to use something like:</p>
<pre class="programlisting">
FETCH_CMD=wget
FETCH_BEFORE_ARGS=--passive-ftp
FETCH_RESUME_ARGS=-c
FETCH_OUTPUT_ARGS=-O
</pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"XFree86-from-pkgsrc" id=
"XFree86-from-pkgsrc"></a>6.6. How can I
install/use XFree86 from pkgsrc?</h2>
</div>
</div>
</div>
<p>If you want to use XFree86 from pkgsrc instead of your
system's own X11 (<code class=
"filename">/usr/X11R6</code>, <code class=
"filename">/usr/openwin</code>, ...), you will have to
add the following line into <code class=
"filename">/etc/mk.conf</code>:</p>
<pre class="programlisting">
X11_TYPE=XFree86
</pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"x.org-from-pkgsrc" id=
"x.org-from-pkgsrc"></a>6.7. How can I
install/use X.org from pkgsrc?</h2>
</div>
</div>
</div>
<p>If you want to use X.org from pkgsrc instead of your
system's own X11 (<code class=
"filename">/usr/X11R6</code>, <code class=
"filename">/usr/openwin</code>, ...) you will have to add
the following line into <code class=
"filename">/etc/mk.conf</code>:</p>
<pre class="programlisting">
X11_TYPE=xorg
</pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"fetch-behind-firewall" id=
"fetch-behind-firewall"></a>6.8. How to fetch
files from behind a firewall</h2>
</div>
</div>
</div>
<p>If you are sitting behind a firewall which does not
allow direct connections to Internet hosts (i.e.
non-NAT), you may specify the relevant proxy hosts. This
is done using an environment variable in the form of a
URL e.g. in Amdahl, the machine “<span class=
"quote">orpheus.amdahl.com</span>” is one of the
firewalls, and it uses port 80 as the proxy port number.
So the proxy environment variables are:</p>
<pre class="programlisting">
ftp_proxy=ftp://orpheus.amdahl.com:80/
http_proxy=http://orpheus.amdahl.com:80/
</pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"passive-ftp" id="passive-ftp"></a>6.9. How do
I tell <span><strong class="command">make
fetch</strong></span> to do passive FTP?</h2>
</div>
</div>
</div>
<p>This depends on which utility is used to retrieve
distfiles. From <code class="filename">bsd.pkg.mk</code>,
<code class="varname">FETCH_CMD</code> is assigned the
first available command from the following list:</p>
<pre class="programlisting">
${LOCALBASE}/bin/ftp
/usr/bin/ftp
</pre>
<p>On a default NetBSD installation, this will be
<code class="filename">/usr/bin/ftp</code>, which
automatically tries passive connections first, and falls
back to active connections if the server refuses to do
passive. For the other tools, add the following to your
<code class="filename">/etc/mk.conf</code> file:
<code class="varname">PASSIVE_FETCH=1</code>.</p>
<p>Having that option present will prevent <code class=
"filename">/usr/bin/ftp</code> from falling back to
active transfers.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"fetching-all-distfiles" id=
"fetching-all-distfiles"></a>6.10. How to
fetch all distfiles at once</h2>
</div>
</div>
</div>
<p>You would like to download all the distfiles in a
single batch from work or university, where you can't run
a <span><strong class="command">make
fetch</strong></span>. There is an archive of distfiles
on <a href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/distfiles/"
target="_top">ftp.NetBSD.org</a>, but downloading the
entire directory may not be appropriate.</p>
<p>The answer here is to do a <span><strong class=
"command">make fetch-list</strong></span> in <code class=
"filename">/usr/pkgsrc</code> or one of it's
subdirectories, carry the resulting list to your machine
at work/school and use it there. If you don't have a
NetBSD-compatible <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?ftp+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">ftp</span>(1)</span></a> (like lukemftp)
at work, don't forget to set <code class=
"varname">FETCH_CMD</code> to something that fetches a
URL:</p>
<p>At home:</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>cd /usr/pkgsrc</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>make fetch-list FETCH_CMD=wget DISTDIR=/tmp/distfiles >/tmp/fetch.sh</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>scp /tmp/fetch.sh work:/tmp</code></strong>
</pre>
<p>At work:</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>sh /tmp/fetch.sh</code></strong>
</pre>
<p>then tar up <code class=
"filename">/tmp/distfiles</code> and take it home.</p>
<p>If you have a machine running NetBSD, and you want to
get <span class="emphasis"><em>all</em></span> distfiles
(even ones that aren't for your machine architecture),
you can do so by using the above-mentioned
<span><strong class="command">make
fetch-list</strong></span> approach, or fetch the
distfiles directly by running:</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>make mirror-distfiles</code></strong>
</pre>
<p>If you even decide to ignore <code class=
"varname">NO_{SRC,BIN}_ON_{FTP,CDROM}</code>, then you
can get everything by running:</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>make fetch NO_SKIP=yes</code></strong>
</pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"tmac.andoc-missing" id=
"tmac.andoc-missing"></a>6.11. What does
“<span class="quote">Don't know how to make
/usr/share/tmac/tmac.andoc</span>” mean?</h2>
</div>
</div>
</div>
<p>When compiling the <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_install/README.html"
class="pkgname">pkgtools/pkg_install</a> package, you get
the error from make that it doesn't know how to make
<code class="filename">/usr/share/tmac/tmac.andoc</code>?
This indicates that you don't have installed the
“<span class="quote">text</span>” set (nroff,
...) from the NetBSD base distribution on your machine.
It is recommended to do that to format manpages.</p>
<p>In the case of the <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_install/README.html"
class="pkgname">pkgtools/pkg_install</a> package, you can
get away with setting <code class=
"varname">NOMAN=YES</code> either in the environment or
in <code class="filename">/etc/mk.conf</code>.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"bsd.own.mk-missing" id=
"bsd.own.mk-missing"></a>6.12. What does
“<span class="quote">Could not find
bsd.own.mk</span>” mean?</h2>
</div>
</div>
</div>
<p>You didn't install the compiler set, <code class=
"filename">comp.tgz</code>, when you installed your
NetBSD machine. Please get it and install it, by
extracting it in <code class="filename">/</code>:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cd /</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>tar --unlink -zxvpf .../comp.tgz</code></strong>
</pre>
<p><code class="filename">comp.tgz</code> is part of
every NetBSD release. Get the one that corresponds to
your release (determine via <span><strong class=
"command">uname -r</strong></span>).</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"using-sudo-with-pkgsrc" id=
"using-sudo-with-pkgsrc"></a>6.13. Using
'sudo' with pkgsrc</h2>
</div>
</div>
</div>
<p>When installing packages as non-root user and using
the just-in-time <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?su+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">su</span>(1)</span></a> feature of
pkgsrc, it can become annoying to type in the root
password for each required package installed. To avoid
this, the sudo package can be used, which does password
caching over a limited time. To use it, install sudo
(either as binary package or from <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/sudo/README.html"
class="pkgname">security/sudo</a>) and then put the
following into your <code class=
"filename">/etc/mk.conf</code>:</p>
<pre class="programlisting">
.if exists(${LOCALBASE}/bin/sudo)
SU_CMD=${LOCALBASE}/bin/sudo /bin/sh -c
.endif
</pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"faq.conf" id=
"faq.conf"></a>6.14. Configuration files
handling and placement</h2>
</div>
</div>
</div>
<p>The global variable <code class=
"varname">PKG_SYSCONFBASE</code> (and some others) can be
set by the system administrator in <code class=
"filename">/etc/mk.conf</code> to define the place where
configuration files get installed. Therefore, packages
must be adapted to support this feature. Keep in mind
that you should only install files that are strictly
necessary in the configuration directory, files that can
go to <code class="filename">$PREFIX/share</code> should
go there.</p>
<p>We will take a look at available variables first
(<code class="filename">bsd.pkg.mk</code> contains more
information). <code class="varname">PKG_SYSCONFDIR</code>
is where the configuration files for a package may be
found (that is, the full path, e.g. <code class=
"filename">/etc</code> or <code class=
"filename">/usr/pkg/etc</code>). This value may be
customized in various ways:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p><code class="varname">PKG_SYSCONFBASE</code> is
the main config directory under which all package
configuration files are to be found. Users will
typically want to set it to <code class=
"filename">/etc</code>, or accept the default
location of <code class=
"filename">$PREFIX/etc</code>.</p>
</li>
<li>
<p><code class="varname">PKG_SYSCONFSUBDIR</code>
is the subdirectory of <code class=
"varname">PKG_SYSCONFBASE</code> under which the
configuration files for a particular package may be
found. Defaults to <code class=
"varname">${SYSCONFBASE}</code>.</p>
</li>
<li>
<p><code class="varname">PKG_SYSCONFVAR</code> is
the special suffix used to distinguish any
overriding values for a particular package (see
next item). It defaults to <code class=
"varname">${PKGBASE}</code>, but for a collection
of related packages that should all have the same
<code class="varname">PKG_SYSCONFDIR</code> value,
it can be set in each of the package Makefiles to a
common value.</p>
</li>
<li>
<p><code class=
"varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code>
overrides the value of <code class=
"varname">${PKG_SYSCONFDIR}</code> for packages
with the same value for <code class=
"varname">PKG_SYSCONFVAR</code>.</p>
<p>As an example, all the various KDE packages may
want to set <code class=
"varname">PKG_SYSCONFVAR</code> to
“<span class="quote">kde</span>” so
admins can set <code class=
"varname">PKG_SYSCONFDIR.kde</code> in <code class=
"filename">/etc/mk.conf</code> to define where to
install KDE config files.</p>
</li>
</ol>
</div>
<p>Programs' configuration directory should be defined
during the configure stage. Packages that use GNU
autoconf can usually do this by using the
“<span class="quote">--sysconfdir</span>”
parameter, but this brings some problems as we will see
now. When you change this pathname in packages, you
should not allow them to install files in that directory
directly. Instead they need to install those files under
<code class="filename">share/examples/${PKGNAME}</code>
so <code class="filename">PLIST</code> can register
them.</p>
<p>Once you have the required configuration files in
place (under the <code class=
"filename">share/examples</code> directory) the variable
<code class="varname">CONF_FILES</code> should be set to
copy them into <code class=
"varname">PKG_SYSCONFDIR</code>. The contents of this
variable is formed by pairs of filenames; the first
element of the pair specifies the file inside the
examples directory (registered by <code class=
"filename">PLIST</code>) and the second element specifies
the target file. This is done this way to allow binary
packages to place files in the right directory using
<code class="filename">INSTALL</code>/<code class=
"filename">DEINSTALL</code> scripts which are created
automatically. The package <code class=
"filename">Makefile</code> must also set <code class=
"varname">USE_PKGINSTALL=YES</code> to use these
automatically generated scripts. The automatic copying of
config files can be toggled by setting the environment
variable <code class="varname">PKG_CONFIG</code> prior to
package installation.</p>
<p>Here is an example, taken from mail/mutt/Makefile:</p>
<pre class="programlisting">
EGDIR= ${PREFIX}/share/doc/mutt/samples
CONF_FILES= ${EGDIR}/Muttrc ${PKG_SYSCONFDIR}/Muttrc
</pre>
<p>As you can see, this package installs configuration
files inside <code class="varname">EGDIR</code>, which
are registered by <code class="filename">PLIST</code>.
After that, the variable <code class=
"varname">CONF_FILES</code> lists the installed file
first and then the target file. Users will also get an
automatic message when files are installed using this
method.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"audit-packages" id=
"audit-packages"></a>6.15. Automated security
checks</h2>
</div>
</div>
</div>
<p>Please be aware that there can often be bugs in
third-party software, and some of these bugs can leave a
machine vulnerable to exploitation by attackers. In an
effort to lessen the exposure, the NetBSD packages team
maintains a database of known-exploits to packages which
have at one time been included in pkgsrc. The database
can be downloaded automatically, and a security audit of
all packages installed on a system can take place. To do
this, install the <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/audit-packages/README.html"
class="pkgname">security/audit-packages</a> package. It
has two components:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>“<span class=
"quote">download-vulnerability-list</span>”,
an easy way to download a list of the security
vulnerabilities information. This list is kept up
to date by the NetBSD security officer and the
NetBSD packages team, and is distributed from the
NetBSD ftp server:</p>
<p><a href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/distfiles/pkg-vulnerabilities"
target=
"_top">ftp://ftp.NetBSD.org/pub/NetBSD/packages/distfiles/pkg-vulnerabilities</a></p>
</li>
<li>
<p>“<span class=
"quote">audit-packages</span>”, an easy way
to audit the current machine, checking each
vulnerability which is known. If a vulnerable
package is installed, it will be shown by output to
stdout, including a description of the type of
vulnerability, and a URL containing more
information.</p>
</li>
</ol>
</div>
<p>Use of the <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/audit-packages/README.html"
class="pkgname">security/audit-packages</a> package is
strongly recommended! After “<span class=
"quote">audit-packages</span>” is installed, please
read the package's message, which you can get by running
<strong class="userinput"><code>pkg_info -D
audit-package</code></strong>.</p>
</div>
</div>
</div>
<div class="part" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h1 class="title"><a name="developers-guide" id=
"developers-guide"></a>The pkgsrc developer's
guide</h1>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="chapter"><a href="#components">7.
Package components - files, directories and
contents</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#components.Makefile">7.1. <code class=
"filename">Makefile</code></a></span></dt>
<dt><span class="sect1"><a href=
"#components.distinfo">7.2. <code class=
"filename">distinfo</code></a></span></dt>
<dt><span class="sect1"><a href=
"#components.patches">7.3. patches/*</a></span></dt>
<dt><span class="sect1"><a href=
"#other-mandatory-files">7.4. Other mandatory
files</a></span></dt>
<dt><span class="sect1"><a href=
"#components.optional">7.5. Optional
files</a></span></dt>
<dt><span class="sect1"><a href="#work-dir">7.6.
<code class="filename">work*</code></a></span></dt>
<dt><span class="sect1"><a href="#files-dir">7.7.
<code class="filename">files/*</code></a></span></dt>
</dl>
</dd>
<dt><span class="chapter"><a href="#makefile">8.
Programming in <code class=
"filename">Makefile</code>s</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#makefile.variables">8.1. <code class=
"filename">Makefile</code> variables</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#makefile.variables.names">8.1.1. Naming
conventions</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href="#makefile.code">8.2.
Code snippets</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#adding-to-list">8.2.1. Adding things to a
list</a></span></dt>
<dt><span class="sect2"><a href=
"#converting-internal-to-external">8.2.2.
Converting an internal list into an external
list</a></span></dt>
<dt><span class="sect2"><a href=
"#passing-variable-to-shell">8.2.3. Passing
variables to a shell command</a></span></dt>
<dt><span class="sect2"><a href=
"#quoting-guideline">8.2.4. Quoting
guideline</a></span></dt>
<dt><span class="sect2"><a href=
"#bsd-make-bug-workaround">8.2.5. Workaround for
a bug in BSD Make</a></span></dt>
</dl>
</dd>
</dl>
</dd>
<dt><span class="chapter"><a href="#plist">9. PLIST
issues</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href="#rcs-id">9.1. RCS
ID</a></span></dt>
<dt><span class="sect1"><a href=
"#automatic-plist-generation">9.2. Semi-automatic
<code class="filename">PLIST</code>
generation</a></span></dt>
<dt><span class="sect1"><a href="#print-PLIST">9.3.
Tweaking output of <span><strong class="command">make
print-PLIST</strong></span></a></span></dt>
<dt><span class="sect1"><a href="#plist.misc">9.4.
Variable substitution in PLIST</a></span></dt>
<dt><span class="sect1"><a href=
"#manpage-compression">9.5.
Manpage-compression</a></span></dt>
<dt><span class="sect1"><a href=
"#using-PLIST_SRC">9.6. Changing PLIST source with
<code class=
"varname">PLIST_SRC</code></a></span></dt>
<dt><span class="sect1"><a href=
"#platform-specific-plist">9.7. Platform specific and
differing PLISTs</a></span></dt>
<dt><span class="sect1"><a href=
"#faq.common-dirs">9.8. Sharing directories between
packages</a></span></dt>
</dl>
</dd>
<dt><span class="chapter"><a href="#buildlink">10.
Buildlink methodology</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#converting-to-buildlink3">10.1. Converting packages
to use buildlink3</a></span></dt>
<dt><span class="sect1"><a href=
"#creating-buildlink3.mk">10.2. Writing <code class=
"filename">buildlink3.mk</code> files</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#anatomy-of-bl3">10.2.1. Anatomy of a
buildlink3.mk file</a></span></dt>
<dt><span class="sect2"><a href=
"#updating-buildlink-depends">10.2.2. Updating
<code class=
"varname">BUILDLINK_DEPENDS.<em class="replaceable">
<code>pkg</code></em></code> in <code class=
"filename">buildlink3.mk</code>
files</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#writing-builtin.mk">10.3. Writing <code class=
"filename">builtin.mk</code> files</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#anatomy-of-builtin.mk">10.3.1. Anatomy of a
<code class="filename">builtin.mk</code>
file</a></span></dt>
<dt><span class="sect2"><a href=
"#native-or-pkgsrc-preference">10.3.2. Global
preferences for native or pkgsrc
software</a></span></dt>
</dl>
</dd>
</dl>
</dd>
<dt><span class="chapter"><a href="#options">11. Options
handling</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#global-default-options">11.1. Global default
options</a></span></dt>
<dt><span class="sect1"><a href=
"#converting-to-options">11.2. Converting packages to
use <code class=
"filename">bsd.options.mk</code></a></span></dt>
</dl>
</dd>
<dt><span class="chapter"><a href="#build">12. The build
process</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href="#build.prefix">12.1.
Program location</a></span></dt>
<dt><span class="sect1"><a href="#main-targets">12.2.
Main targets</a></span></dt>
<dt><span class="sect1"><a href=
"#build.helpful-targets">12.3. Other helpful
targets</a></span></dt>
</dl>
</dd>
<dt><span class="chapter"><a href="#fixes">13. Notes on
fixes for packages</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#general-operation">13.1. General
operation</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#pulling-vars-from-etc-mk.conf">13.1.1. How to
pull in variables from
/etc/mk.conf</a></span></dt>
<dt><span class="sect2"><a href=
"#where-to-install-documentation">13.1.2. Where
to install documentation</a></span></dt>
<dt><span class="sect2"><a href=
"#restricted-packages">13.1.3. Restricted
packages</a></span></dt>
<dt><span class="sect2"><a href=
"#dependencies">13.1.4. Handling
dependencies</a></span></dt>
<dt><span class="sect2"><a href=
"#conflicts">13.1.5. Handling conflicts with
other packages</a></span></dt>
<dt><span class="sect2"><a href=
"#not-building-packages">13.1.6. Packages that
cannot or should not be built</a></span></dt>
<dt><span class="sect2"><a href=
"#undeletable-packages">13.1.7. Packages which
should not be deleted, once
installed</a></span></dt>
<dt><span class="sect2"><a href=
"#security-handling">13.1.8. Handling packages
with security problems</a></span></dt>
<dt><span class="sect2"><a href=
"#compiler-bugs">13.1.9. How to handle compiler
bugs</a></span></dt>
<dt><span class="sect2"><a href=
"#bumping-pkgrevision">13.1.10. How to handle
incrementing versions when fixing an existing
package</a></span></dt>
<dt><span class="sect2"><a href=
"#portability-of-packages">13.1.11. Portability
of packages</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#downloading-issues">13.2. Possible downloading
issues</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#no-plain-download">13.2.1. Packages whose
distfiles aren't available for plain
downloading</a></span></dt>
<dt><span class="sect2"><a href=
"#modified-distfiles-same-name">13.2.2. How to
handle modified distfiles with the 'old'
name</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#configuration-gotchas">13.3. Configuration
gotchas</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#fixes.libtool">13.3.1. Shared libraries -
libtool</a></span></dt>
<dt><span class="sect2"><a href=
"#using-libtool">13.3.2. Using libtool on GNU
packages that already support
libtool</a></span></dt>
<dt><span class="sect2"><a href=
"#autoconf-automake">13.3.3. GNU
Autoconf/Automake</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#building-considerations">13.4. Building
considerations</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#cpp-defines">13.4.1. CPP
defines</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#package-specific-actions">13.5. Package specific
actions</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#package-configuration-files">13.5.1. Package
configuration files</a></span></dt>
<dt><span class="sect2"><a href=
"#user-interaction">13.5.2. User
interaction</a></span></dt>
<dt><span class="sect2"><a href=
"#handling-licenses">13.5.3. Handling
licenses</a></span></dt>
<dt><span class="sect2"><a href=
"#creating-accounts">13.5.4. Creating an account
from a package</a></span></dt>
<dt><span class="sect2"><a href=
"#installing-score-files">13.5.5. Installing
score files</a></span></dt>
<dt><span class="sect2"><a href=
"#login-shells">13.5.6. Packages providing login
shells</a></span></dt>
<dt><span class="sect2"><a href=
"#perl-scripts">13.5.7. Packages containing perl
scripts</a></span></dt>
<dt><span class="sect2"><a href=
"#hardcoded-paths">13.5.8. Packages with
hardcoded paths to other
interpreters</a></span></dt>
<dt><span class="sect2"><a href=
"#perl-modules">13.5.9. Packages installing perl
modules</a></span></dt>
<dt><span class="sect2"><a href=
"#faq.info-files">13.5.10. Packages installing
info files</a></span></dt>
<dt><span class="sect2"><a href=
"#gconf2-data-files">13.5.11. Packages installing
GConf2 data files</a></span></dt>
<dt><span class="sect2"><a href=
"#scrollkeeper-data-files">13.5.12. Packages
installing scrollkeeper data
files</a></span></dt>
<dt><span class="sect2"><a href=
"#x11-fonts">13.5.13. Packages installing X11
fonts</a></span></dt>
<dt><span class="sect2"><a href=
"#gtk2-modules">13.5.14. Packages installing GTK2
modules</a></span></dt>
<dt><span class="sect2"><a href=
"#sgml-xml-data">13.5.15. Packages installing
SGML or XML data</a></span></dt>
<dt><span class="sect2"><a href=
"#mime-database">13.5.16. Packages installing
extensions to the MIME database</a></span></dt>
<dt><span class="sect2"><a href=
"#intltool">13.5.17. Packages using
intltool</a></span></dt>
<dt><span class="sect2"><a href=
"#startup-scripts">13.5.18. Packages installing
startup scripts</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#feedback-to-author">13.6. Feedback to the
author</a></span></dt>
</dl>
</dd>
<dt><span class="chapter"><a href="#debug">14.
Debugging</a></span></dt>
<dt><span class="chapter"><a href="#submit">15.
Submitting and Committing</a></span></dt>
<dd>
<dl>
<dt><span class="sect1"><a href=
"#submitting-your-package">15.1. Submitting your
packages</a></span></dt>
<dt><span class="sect1"><a href=
"#committing-importing">15.2. Committing: Importing a
package into CVS</a></span></dt>
<dt><span class="sect1"><a href=
"#updating-package">15.3. Updating a package to a
newer version</a></span></dt>
<dt><span class="sect1"><a href=
"#moving-package">15.4. Moving a package in
pkgsrc</a></span></dt>
</dl>
</dd>
</dl>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="components" id=
"components"></a>Chapter 7. Package
components - files, directories and contents</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href=
"#components.Makefile">7.1. <code class=
"filename">Makefile</code></a></span></dt>
<dt><span class="sect1"><a href=
"#components.distinfo">7.2. <code class=
"filename">distinfo</code></a></span></dt>
<dt><span class="sect1"><a href=
"#components.patches">7.3. patches/*</a></span></dt>
<dt><span class="sect1"><a href=
"#other-mandatory-files">7.4. Other mandatory
files</a></span></dt>
<dt><span class="sect1"><a href=
"#components.optional">7.5. Optional
files</a></span></dt>
<dt><span class="sect1"><a href="#work-dir">7.6.
<code class="filename">work*</code></a></span></dt>
<dt><span class="sect1"><a href="#files-dir">7.7.
<code class="filename">files/*</code></a></span></dt>
</dl>
</div>
<p>Whenever you're preparing a package, there are a number
of files involved which are described in the following
sections.</p>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"components.Makefile" id=
"components.Makefile"></a>7.1. <code class=
"filename">Makefile</code></h2>
</div>
</div>
</div>
<p>Building, installation and creation of a binary
package are all controlled by the package's <code class=
"filename">Makefile</code>. The <code class=
"filename">Makefile</code> describes various things about
a package, for example from where to get it, how to
configure, build, and install it.</p>
<p>A package <code class="filename">Makefile</code>
contains several sections that describe the package.</p>
<p>In the first section there are the following
variables, which should appear exactly in the order given
here.</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><code class="varname">DISTNAME</code> is the
basename of the distribution file to be downloaded
from the package's website.</p>
</li>
<li>
<p><code class="varname">PKGNAME</code> is the name
of the package, as used by pkgsrc. You only need to
provide it if it differs from DISTNAME. Usually it
is the directory name together with the version
number. It must match the regular expression
<code class=
"varname">^[A-Za-z0-9][A-Za-z0-9-_.+]*$</code>,
that is, it starts with a letter or digit, and
contains only letters, digits, dashes, underscores,
dots and plus signs.</p>
</li>
<li>
<p><code class="varname">CATEGORIES</code> is a
list of categories which the package fits in. You
can choose any of the top-level directories of
pkgsrc for it.</p>
</li>
<li>
<p><code class="varname">MASTER_SITES</code> is a
list of URLs where the distribution files can be
downloaded. Each URL must end with a slash.</p>
</li>
</ul>
</div>
<p>The second section contains the following
variables.</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><code class="varname">MAINTAINER</code> is the
mail address of the package's maintainer, which is
the person you can contact when the package does
not work.</p>
</li>
<li>
<p><code class="varname">HOMEPAGE</code> is a URL
where users can find more information about the
package.</p>
</li>
<li>
<p><code class="varname">COMMENT</code> is a
one-line comment about the purpose of the
package.</p>
</li>
</ul>
</div>
<p>The <code class="varname">MASTER_SITES</code> may be
set to one of the predefined sites:</p>
<pre class="programlisting">
${MASTER_SITE_APACHE}
${MASTER_SITE_BACKUP}
${MASTER_SITE_CYGWIN}
${MASTER_SITE_DEBIAN}
${MASTER_SITE_FREEBSD}
${MASTER_SITE_FREEBSD_LOCAL}
${MASTER_SITE_GNOME}
${MASTER_SITE_GNU}
${MASTER_SITE_GNUSTEP}
${MASTER_SITE_IFARCHIVE}
${MASTER_SITE_MOZILLA}
${MASTER_SITE_OPENOFFICE}
${MASTER_SITE_PERL_CPAN}
${MASTER_SITE_R_CRAN}
${MASTER_SITE_SOURCEFORGE}
${MASTER_SITE_SUNSITE}
${MASTER_SITE_SUSE}
${MASTER_SITE_TEX_CTAN}
${MASTER_SITE_XCONTRIB}
${MASTER_SITE_XEMACS}
</pre>
<p>If one of these predefined sites is chosen, you may
require the ability to specify a subdirectory of that
site. Since these macros may expand to more than one
actual site, you <span class=
"emphasis"><em>must</em></span> use the following
construct to specify a subdirectory:</p>
<pre class="programlisting">
${MASTER_SITE_GNU:=subdirectory/name/}
${MASTER_SITE_SOURCEFORGE:=project_name/}
</pre>
<p>Note the trailing slash after the subdirectory
name.</p>
<div class="note" style=
"margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p><code class="varname">MASTER_SITE_SUBDIR</code> has
been deprecated and <span class="emphasis"><em>should
no longer be used</em></span>.</p>
</div>
<p>If the package has multiple <code class=
"varname">DISTFILES</code> or multiple <code class=
"varname">PATCHFILES</code> from different sites, set
<code class="varname">SITES_foo</code> to a list of URI's
where file “<span class="quote">foo</span>”
may be found. “<span class=
"quote">foo</span>” includes the suffix, e.g.</p>
<pre class="programlisting">
DISTFILES= ${DISTNAME}${EXTRACT_SUFX}
DISTFILES+= foo-file.tar.gz
SITES_foo-file.tar.gz=http://www.somewhere.com/somehow/ \
http://www.somewhereelse.com/mirror/somehow/
</pre>
<p>Note that the normal default setting of <code class=
"varname">DISTFILES</code> must be made explicit if you
want to add to it (rather than replace it), as you
usually would.</p>
<p>Currently the following values are available for
<code class="varname">CATEGORIES</code>. If more than one
is used, they need to be separated by spaces:</p>
<pre class="programlisting">
archivers cross geography meta-pkgs security
audio databases graphics misc shells
benchmarks devel ham multimedia sysutils
biology editors inputmethod net textproc
cad emulators lang news time
chat finance mail parallel wm
comms fonts math pkgtools www
converters games mbone print x11
</pre>
<p>Please pay attention to the following gotchas:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>Add <code class="varname">MANCOMPRESSED</code>
if manpages are installed in compressed form by the
package; see comment in <code class=
"filename">bsd.pkg.mk</code>.</p>
</li>
<li>
<p>Replace <code class="filename">/usr/local</code>
with “<span class=
"quote">${PREFIX}</span>” in all files (see
patches, below).</p>
</li>
<li>
<p>If the package installs any info files, see
<a href="#faq.info-files" title=
"13.5.10. Packages installing info files">Section
13.5.10, “Packages installing info
files”</a>.</p>
</li>
<li>
<p>Set <code class="varname">MAINTAINER</code> to
be yourself. If you really can't maintain the
package for future updates, set it to <code class=
"email"><<a href=
"mailto:tech-pkg@NetBSD.org">tech-pkg@NetBSD.org</a>></code>.</p>
</li>
<li>
<p>If a home page for the software in question
exists, add the variable <code class=
"varname">HOMEPAGE</code> right after <code class=
"varname">MAINTAINER</code>. The value of this
variable should be the URL for the home page.</p>
</li>
<li>
<p>Be sure to set the <code class=
"varname">COMMENT</code> variable to a short
description of the package, not containing the
pkg's name.</p>
</li>
</ul>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"components.distinfo" id=
"components.distinfo"></a>7.2. <code class=
"filename">distinfo</code></h2>
</div>
</div>
</div>
<p>Most important, the mandatory message digest, or
checksum, of all the distfiles needed for the package to
compile, confirming they match the original file
distributed by the author. This ensures that the distfile
retrieved from the Internet has not been corrupted during
transfer or altered by a malign force to introduce a
security hole. It is generated using the
<span><strong class="command">make
makesum</strong></span> command. The digest algorithm
used was, at one stage, md5, but that was felt lacking
compared to sha1, and so sha1 is now the default
algorithm. The distfile size is also generated and stored
in new distinfo files. The <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/digest/README.html"
class="pkgname">pkgtools/digest</a> utility calculates
all of the digests in the distinfo file, and it provides
various different algorithms. At the current time, the
algorithms provided are: <span class=
"emphasis"><em>md5</em></span>, <span class=
"emphasis"><em>rmd160</em></span>, <span class=
"emphasis"><em>sha1</em></span>, <span class=
"emphasis"><em>sha256</em></span>, <span class=
"emphasis"><em>sha384</em></span> and <span class=
"emphasis"><em>sha512</em></span>.</p>
<p>Some packages have different sets of distfiles on a
per architecture basis, for example <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/navigator/README.html"
class="pkgname">www/navigator</a>). These are kept in the
same distinfo file and care should be taken when
upgrading such a package to ensure distfile information
is not lost.</p>
<p>The message digest/checksum for all the official
patches found in the <code class=
"filename">patches/</code> directory (see <a href=
"#components.patches" title=
"7.3. patches/*">Section 7.3,
“patches/*”</a>) for the package is also
stored in the <code class="filename">distinfo</code>
file. This is a message digest/checksum of all lines in
the patch file except the NetBSD RCS Id. This file is
generated by invoking <span><strong class="command">make
makepatchsum</strong></span> (or <span><strong class=
"command">make mps</strong></span> if you're in a
hurry).</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"components.patches" id=
"components.patches"></a>7.3. patches/*</h2>
</div>
</div>
</div>
<p>This directory contains files that are used by the
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?patch+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">patch</span>(1)</span></a> command to
modify the sources as distributed in the distribution
file into a form that will compile and run perfectly on
NetBSD. The files are applied successively in alphabetic
order (as returned by a shell “<span class=
"quote">patches/patch-*</span>” glob expansion), so
<code class="filename">patch-aa</code> is applied before
<code class="filename">patch-ab</code>, etc.</p>
<p>The <code class="filename">patch-*</code> files should
be in <span><strong class="command">diff
-bu</strong></span> format, and apply without a fuzz to
avoid problems. (To force patches to apply with fuzz you
can set <code class=
"varname">PATCH_FUZZ_FACTOR=-F2</code>). Furthermore, do
not put changes for more than one file into a single
patch-file, as this will make future modifications more
difficult.</p>
<p>Similar, a file should be patched at most once, not
several times by several different patches. If a file
needs several patches, they should be combined into one
file.</p>
<p>One important thing to mention is to pay attention
that no RCS IDs get stored in the patch files, as these
will cause problems when later checked into the NetBSD
CVS tree. Use the <span><strong class=
"command">pkgdiff</strong></span> from the <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdiff/README.html"
class="pkgname">pkgtools/pkgdiff</a> package to avoid
these problems.</p>
<p>For even more automation, we recommend using
<span><strong class="command">mkpatches</strong></span>
from the same package to make a whole set of patches. You
just have to backup files before you edit them to
<code class="filename">filename.orig</code>, e.g. with
<span><strong class="command">cp -p filename
filename.orig</strong></span> or, easier, by using
<span><strong class="command">pkgvi</strong></span> again
from the same package. If you upgrade a package this way,
you can easily compare the new set of patches with the
previously existing one with <span><strong class=
"command">patchdiff</strong></span>.</p>
<p>When you have finished a package, remember to generate
the checksums for the patch files by using the
<span><strong class="command">make
makepatchsum</strong></span> command, see <a href=
"#components.distinfo" title=
"7.2. distinfo">Section 7.2,
“<code class="filename">distinfo</code>”</a>.</p>
<p>Patch files that are distributed by the author or
other maintainers can be listed in <code class=
"varname">$PATCHFILES</code>.</p>
<p>If it is desired to store any patches that should not
be committed into pkgsrc, they can be kept outside the
pkgsrc tree in the <code class=
"filename">$LOCALPATCHES</code> directory. The directory
tree there is expected to have the same
“<span class="quote">category/package</span>”
structure as pkgsrc, and patches are expected to be
stored inside these dirs (also known as <code class=
"filename">$LOCALPATCHES/$PKGPATH</code>). For example if
you want to keep a private patch for <code class=
"filename">pkgsrc/graphics/png</code>, keep it in
<code class=
"filename">$LOCALPATCHES/graphics/png/mypatch</code>. All
files in the named directory are expected to be patch
files, and <span class="emphasis"><em>they are applied
after pkgsrc patches are applied</em></span>.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"other-mandatory-files" id=
"other-mandatory-files"></a>7.4. Other
mandatory files</h2>
</div>
</div>
</div>
<div class="variablelist">
<dl>
<dt><span class="term"><code class=
"filename">DESCR</code></span></dt>
<dd>
<p>A multi-line description of the piece of
software. This should include any credits where
they are due. Please bear in mind that others do
not share your sense of humour (or spelling
idiosyncrasies), and that others will read
everything that you write here.</p>
</dd>
<dt><span class="term"><code class=
"filename">PLIST</code></span></dt>
<dd>
<p>This file governs the files that are installed
on your system: all the binaries, manual pages,
etc. There are other directives which may be
entered in this file, to control the creation and
deletion of directories, and the location of
inserted files. See <a href="#plist" title=
"Chapter 9. PLIST issues">Chapter 9,
<i>PLIST issues</i></a> for more information.</p>
</dd>
</dl>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"components.optional" id=
"components.optional"></a>7.5. Optional
files</h2>
</div>
</div>
</div>
<div class="variablelist">
<dl>
<dt><span class="term"><code class=
"filename">INSTALL</code></span></dt>
<dd>
<p>This shell script is invoked twice by <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_add</span>(1)</span></a>. First
time after package extraction and before files are
moved in place, the second time after the files to
install are moved in place. This can be used to do
any custom procedures not possible with @exec
commands in <code class="filename">PLIST</code>.
See <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_add</span>(1)</span></a> and
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_create</span>(1)</span></a> for
more information.</p>
</dd>
<dt><span class="term"><code class=
"filename">DEINSTALL</code></span></dt>
<dd>
<p>This script is executed before and after any
files are removed. It is this script's
responsibility to clean up any additional messy
details around the package's installation, since
all pkg_delete knows is how to delete the files
created in the original distribution. See <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_delete</span>(1)</span></a> and
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_create</span>(1)</span></a> for
more information.</p>
</dd>
<dt><span class="term"><code class=
"filename">MESSAGE</code></span></dt>
<dd>
<p>Display this file after installation of the
package. Useful for things like legal notices on
almost-free software and hints for updating config
files after installing modules for apache, PHP etc.
Please note that you can modify variables in it
easily by using <code class=
"varname">MESSAGE_SUBST</code> in the package's
<code class="filename">Makefile</code>:</p>
<pre class="programlisting">
MESSAGE_SUBST+= SOMEVAR="somevalue"
</pre>
<p>replaces "${SOMEVAR}" with “<span class=
"quote">somevalue</span>” in <code class=
"filename">MESSAGE</code>.</p>
</dd>
</dl>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"work-dir" id="work-dir"></a>7.6. <code class=
"filename">work*</code></h2>
</div>
</div>
</div>
<p>When you type <span><strong class=
"command">make</strong></span> the distribution files are
unpacked into this directory. It can be removed by
running <span><strong class="command">make
clean</strong></span>. Besides the sources, this
directory is also used to keep various timestamp
files.</p>
<p>If a package doesn't create a subdirectory for itself
(like GNU software does, for instance), but extracts
itself in the current directory, you should set
<code class="varname">WRKSRC</code> accordingly, e.g.
<a xmlns="http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/editors/sam/README.html"
class="pkgname">editors/sam</a> again, but the quick
answer is:</p>
<pre class="programlisting">
WRKSRC= ${WRKDIR}
</pre>
<p>Please note that the old <code class=
"varname">NO_WRKSUBDIR</code> has been deprecated and
should not be used. Also, if your package doesn't create
a subdir with the name of <code class=
"varname">DISTNAME</code> but some different name, set
<code class="varname">WRKSRC</code> to point to the
proper name in <code class="filename">${WRKDIR}</code>.
See <a xmlns="http://www.w3.org/TR/xhtml1/transitional"
href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/lang/tcl/README.html"
class="pkgname">lang/tcl</a> and <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/tk/README.html"
class="pkgname">x11/tk</a> for examples, and here is
another one:</p>
<pre class="programlisting">
WRKSRC= ${WRKDIR}/${DISTNAME}/unix
</pre>
<p>The name of the working directory created by pkgsrc is
<code class="filename">work</code> by default. If the
same pkgsrc tree should be used on several different
platforms, the variable <code class=
"varname">OBJMACHINE</code> can be set in /etc/mk.conf to
attach the platform to the directory name, e.g.
<code class="filename">work.i386</code> or <code class=
"filename">work.sparc</code>.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"files-dir" id=
"files-dir"></a>7.7. <code class=
"filename">files/*</code></h2>
</div>
</div>
</div>
<p>If you have any files that you wish to be placed in
the package prior to configuration or building, you could
place these files here and use a “<span class=
"quote">${CP}</span>” command in the
“<span class="quote">pre-configure</span>”
target to achieve this. Alternatively, you could simply
diff the file against <code class=
"filename">/dev/null</code> and use the patch mechanism
to manage the creation of this file.</p>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="makefile" id=
"makefile"></a>Chapter 8. Programming in
<code class="filename">Makefile</code>s</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href=
"#makefile.variables">8.1. <code class=
"filename">Makefile</code> variables</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#makefile.variables.names">8.1.1. Naming
conventions</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href="#makefile.code">8.2.
Code snippets</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#adding-to-list">8.2.1. Adding things to a
list</a></span></dt>
<dt><span class="sect2"><a href=
"#converting-internal-to-external">8.2.2.
Converting an internal list into an external
list</a></span></dt>
<dt><span class="sect2"><a href=
"#passing-variable-to-shell">8.2.3. Passing
variables to a shell command</a></span></dt>
<dt><span class="sect2"><a href=
"#quoting-guideline">8.2.4. Quoting
guideline</a></span></dt>
<dt><span class="sect2"><a href=
"#bsd-make-bug-workaround">8.2.5. Workaround for a
bug in BSD Make</a></span></dt>
</dl>
</dd>
</dl>
</div>
<p>Pkgsrc consists of many <code class=
"filename">Makefile</code> fragments, each of which forms a
well-defined part of the pkgsrc system. Using the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">make</span>(1)</span></a> system as a
programming language for a big system like pkgsrc requires
some discipline to keep the code correct and
understandable.</p>
<p>The basic ingredients for <code class=
"filename">Makefile</code> programming are variables (which
are actually macros) and shell commands. Among these shell
commands may even be more complex ones like <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?awk+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">awk</span>(1)</span></a> programs. To make
sure that every shell command runs as intended it is
necessary to quote all variables correctly when they are
used.</p>
<p>This chapter describes some patterns, that appear quite
often in <code class="filename">Makefile</code>s, including
the pitfalls that come along with them.</p>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"makefile.variables" id=
"makefile.variables"></a>8.1. <code class=
"filename">Makefile</code> variables</h2>
</div>
</div>
</div>
<p><code class="filename">Makefile</code> variables
contain strings that can be processed using the five
operators ``='', ``+='', ``?='', ``:='', and ``!='',
which are described in the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">make</span>(1)</span></a> man page.</p>
<p>When a variable's value is parsed from a <code class=
"filename">Makefile</code>, the hash character ``#'' and
the backslash character ``\'' are handled specially. If a
backslash is followed by a newline, any whitespace
immediately in front of the backslash, the backslash, the
newline, and any whitespace immediately behind the
newline are replaced with a single space. A backspace
character and an immediately following hash character are
replaced with a single hash character. Otherwise the
backslash is passed as is. In a variable assignment, any
hash character that is not preceded by a backslash starts
a comment that continues upto the end of the logical
line.</p>
<p><span class="emphasis"><em>Note:</em></span> Because
of this parsing algorithm the only way to create a
variable consisting of a single backslash is using the
``!='' operator, for example: <code class=
"varname">BACKSLASH!=echo "\\"</code>.</p>
<p>So far for defining variables. The other thing you can
do with variables is evaluating them. A variable is
evaluated when it is part of the right side of the ``:=''
or the ``!='' operator, or directly before executing a
shell command which the variable is part of. In all other
cases <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">make</span>(1)</span></a> performs lazy
evaluation, that is, variables are not evaluated until
there's no other way. The ``modifiers'' mentioned in the
man page also evaluate the variable.</p>
<p>Some of the modifiers split the string into words and
then operate on the words, others operate on the string
as a whole. When a string is splitted into words, it is
splitted as you would expect it from <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?sh+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">sh</span>(1)</span></a>.</p>
<p>No rule without exception—the
<span><strong class="command">.for</strong></span> loop
does not follow the shell quoting rules but splits at
sequences of whitespace.</p>
<p>There are several types of variables that should be
handled differently. Strings and two types of lists.</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><span class="emphasis"><em>Strings</em></span>
can contain arbitrary characters. Nevertheless you
should restrict yourself to only using printable
characters. Examples are <code class=
"varname">PREFIX</code> and <code class=
"varname">COMMENT</code>.</p>
</li>
<li>
<p><span class="emphasis"><em>Internal
lists</em></span> are lists that are never exported
to any shell command. Their elements are separated
by whitespace. Therefore the elements themselves
cannot have embedded whitespace. Any other
characters are allowed. Internal lists can be used
in <span><strong class=
"command">.for</strong></span> loops. Examples are
<code class="varname">DEPENDS</code> and
<code class="varname">BUILD_DEPENDS</code>.</p>
</li>
<li>
<p><span class="emphasis"><em>External
lists</em></span> are lists that may be exported to
a shell command. Their elements can contain any
characters, including whitespace. That's why they
cannot be used in <span><strong class=
"command">.for</strong></span> loops. Examples are
<code class="varname">DISTFILES</code> and
<code class="varname">MASTER_SITES</code>.</p>
</li>
</ul>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"makefile.variables.names" id=
"makefile.variables.names"></a>8.1.1. Naming
conventions</h3>
</div>
</div>
</div>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>All variable names starting with an underscore
are reserved for use by the pkgsrc
infrastructure. They shall not be used by package
<code class="filename">Makefile</code>s.</p>
</li>
<li>
<p>In <span><strong class=
"command">.for</strong></span> loops you should
use lowercase variable names for the iteration
variables.</p>
</li>
<li>
<p>All list variables should have a ``plural''
name, e.g. <code class=
"varname">PKG_OPTIONS</code> or <code class=
"varname">DISTFILES</code>.</p>
</li>
</ul>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"makefile.code" id=
"makefile.code"></a>8.2. Code snippets</h2>
</div>
</div>
</div>
<p>This section presents you with some code snippets you
should use in your own code. If you don't find anything
appropriate here, you should test your code and add it
here.</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="adding-to-list" id=
"adding-to-list"></a>8.2.1. Adding things to
a list</h3>
</div>
</div>
</div>
<pre class="programlisting">
STRING= foo * bar `date`
INT_LIST= # empty
ANOTHER_INT_LIST= apache-[0-9]*:../../www/apache
EXT_LIST= # empty
ANOTHER_EXT_LIST= a=b c=d
INT_LIST+= ${STRING} # 1
INT_LIST+= ${ANOTHER_INT_LIST} # 2
EXT_LIST+= ${STRING:Q} # 3
EXT_LIST+= ${ANOTHER_EXT_LIST} # 4
</pre>
<p>When you add a string to an external list (example
3), it must be quoted. In all other cases, you must not
add a quoting level. You must not merge internal and
external lists, unless you are sure that all entries
are correctly interpreted in both lists.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"converting-internal-to-external" id=
"converting-internal-to-external"></a>8.2.2. Converting
an internal list into an external list</h3>
</div>
</div>
</div>
<pre class="programlisting">
EXT_LIST= # empty
.for i in ${INT_LIST}
EXT_LIST+= ${i:Q}""
.endfor
</pre>
<p>This code converts the internal list <code class=
"varname">INT_LIST</code> into the external list
<code class="varname">EXT_LIST</code>. As the elements
of an internal list are unquoted they must be quoted
here. The reason for appending <code class=
"varname">""</code> is explained below.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"passing-variable-to-shell" id=
"passing-variable-to-shell"></a>8.2.3. Passing
variables to a shell command</h3>
</div>
</div>
</div>
<pre class="programlisting">
STRING= foo bar < > * `date` $$HOME ' "
EXT_LIST= string=${STRING:Q} x=second\ item
all:
echo ${STRING} # 1
echo "${STRING}" # 2
echo "${STRING:Q}" # 3
echo ${STRING:Q} # 4
echo x${STRING:Q} | sed 1s,.,, # 5
env ${EXT_LIST} /bin/sh -c 'echo "$$string"; echo "$$x"'
</pre>
<p>Example 1 leads to a syntax error in the shell, as
the characters are just copied.</p>
<p>Example 2 leads to a syntax error too, and if you
leave out the last " character from <code class=
"varname">${STRING}</code>, <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?date+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">date</span>(1)</span></a> will be
executed. The <code class="varname">$HOME</code> shell
variable would be evaluated, too.</p>
<p>Example 3 outputs each space character preceded by a
backslash (or not), depending on the implementation of
the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?echo+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">echo</span>(1)</span></a> command.</p>
<p>Example 4 handles correctly every string that does
not start with a dash. In that case, the result depends
on the implementation of the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?echo+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">echo</span>(1)</span></a> command. As
long as you can guarantee that your input does not
start with a dash this form is appropriate.</p>
<p>Example 5 handles even the case of a leading dash
correctly.</p>
<p>The <code class="varname">EXT_LIST</code> does not
need to be quoted because the quoting has already be
done when adding elements to the list.</p>
<p>As internal lists shall not be passed to the shell,
there is no example for it.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="quoting-guideline" id=
"quoting-guideline"></a>8.2.4. Quoting
guideline</h3>
</div>
</div>
</div>
<p>There are many possible sources of wrongly quoted
variables. This section lists some of the commonly
known ones.</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>Whenever you use the value of a list, think
about what happens to leading or trailing
whitespace. If the list is a well-formed shell
expression you can apply the <code class=
"varname">:M*</code> modifier to strip leading
and trailing whitespace from each word. The
<code class="varname">:M</code> operator first
splits its argument according to the rules of the
shell, and then creates a new list consisting of
all words that match the shell glob expression
<code class="varname">*</code>, that is: all. One
class of situations where this is needed is when
adding a variable like <code class=
"varname">CPPFLAGS</code> to <code class=
"varname">CONFIGURE_ARGS</code>. If the configure
script invokes other configure scripts it strips
the leading and trailing whitespace from the
variable and then passes it to the other
configure scripts. But these configure scripts
expect the (child) <code class=
"varname">CPPFLAGS</code> variable to be the same
as the parent <code class=
"varname">CPPFLAGS</code>. That's why we better
pass the <code class="varname">CPPFLAGS</code>
value properly trimmed. And here is how we do
it:</p>
<pre class="programlisting">
CPPFLAGS= # empty
CPPFLAGS+= -Wundef -DPREFIX=\"${PREFIX:Q}\"
CPPFLAGS+= ${MY_CPPFLAGS}
CONFIGURE_ARGS+= CPPFLAGS=${CPPFLAGS:M*:Q}
all:
echo x${CPPFLAGS:Q}x # leading and trailing whitespace
echo x${CONFIGURE_ARGS}x # properly trimmed
</pre>
</li>
<li>
<p>The example above contains one bug: The
<code class="varname">${PREFIX}</code> is a
properly quoted shell expression, but there is
the C compiler after it, which also expects a
properly quoted string (this time in C syntax).
The version above is therefore only correct if
<code class="varname">${PREFIX}</code> does not
have embedded backslashes or double quotes. If
you want to allow these, you have to add another
layer of quoting to each variable that is used as
a C string literal. You cannot use the
<code class="varname">:Q</code> operator for it,
as this operator only works for the shell.</p>
</li>
<li>
<p>Whenever a variable can be empty the
<code class="varname">:Q</code> operator can have
surprising results. Here are two completely
different cases which can be solved with the same
trick.</p>
<pre class="programlisting">
EMPTY= # empty
empty_test:
for i in a ${EMPTY:Q} c; do \
echo "$$i"; \
done
for_test:
.for i in a:\ a:\test.txt
echo ${i:Q}
echo "foo"
.endfor
</pre>
<p>The first example will only print two of the
three lines we might have expected. This is
because <code class="varname">${EMPTY:Q}</code>
expands to the empty string, which the shell
cannot see. The workaround is to write
<code class="varname">${EMPTY:Q}""</code>. This
pattern can be often found as <code class=
"varname">${TEST} -z ${VAR:Q}</code> or as
<code class="varname">${TEST} -f
${FNAME:Q}</code> (both of these are wrong).</p>
<p>The second example will only print three lines
instead of four. The first line looks like
<code class="varname">a:\ echo foo</code>. This
is because the backslash of the value
<code class="varname">a:\</code> is interpreted
as a line-continuation by <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">make</span>(1)</span></a>, which
makes the second line the arguments of the
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?echo+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">echo</span>(1)</span></a> command
from the first line. To avoid this, write
<code class="varname">${i:Q}""</code>.</p>
</li>
</ul>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"bsd-make-bug-workaround" id=
"bsd-make-bug-workaround"></a>8.2.5. Workaround
for a bug in BSD Make</h3>
</div>
</div>
</div>
<p>The pkgsrc bmake program does not handle the
following assignment correctly. In case <code class=
"varname">_othervar_</code> contains a ``-'' character,
one of the closing braces is included in <code class=
"varname">${VAR}</code> after this code executes.</p>
<pre class="programlisting">
VAR:= ${VAR:N${_othervar_:C/-//}}
</pre>
<p>For a more complex code snippet and a workaround,
see the package <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/regress/make-quoting/README.html"
class="pkgname">regress/make-quoting</a>, testcase
<code class="varname">bug1</code>.</p>
</div>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="plist" id=
"plist"></a>Chapter 9. PLIST issues</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href="#rcs-id">9.1. RCS
ID</a></span></dt>
<dt><span class="sect1"><a href=
"#automatic-plist-generation">9.2. Semi-automatic
<code class="filename">PLIST</code>
generation</a></span></dt>
<dt><span class="sect1"><a href="#print-PLIST">9.3.
Tweaking output of <span><strong class="command">make
print-PLIST</strong></span></a></span></dt>
<dt><span class="sect1"><a href="#plist.misc">9.4.
Variable substitution in PLIST</a></span></dt>
<dt><span class="sect1"><a href=
"#manpage-compression">9.5.
Manpage-compression</a></span></dt>
<dt><span class="sect1"><a href="#using-PLIST_SRC">9.6.
Changing PLIST source with <code class=
"varname">PLIST_SRC</code></a></span></dt>
<dt><span class="sect1"><a href=
"#platform-specific-plist">9.7. Platform specific and
differing PLISTs</a></span></dt>
<dt><span class="sect1"><a href="#faq.common-dirs">9.8.
Sharing directories between packages</a></span></dt>
</dl>
</div>
<p>The <code class="filename">PLIST</code> file contains a
package's “<span class="quote">packing
list</span>”, i.e. a list of files that belong to the
package (relative to the <code class=
"filename">${PREFIX}</code> directory it's been installed
in) plus some additional statements - see the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_create</span>(1)</span></a> manpage for
a full list. This chapter addresses some issues that need
attention when dealing with the <code class=
"filename">PLIST</code> file (or files, see below!).</p>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"rcs-id" id="rcs-id"></a>9.1. RCS ID</h2>
</div>
</div>
</div>
<p>Be sure to add a RCS ID line as the first thing in any
<code class="filename">PLIST</code> file you write:</p>
<pre class="programlisting">
@comment $NetBSD$
</pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"automatic-plist-generation" id=
"automatic-plist-generation"></a>9.2. Semi-automatic
<code class="filename">PLIST</code> generation</h2>
</div>
</div>
</div>
<p>You can use the <span><strong class="command">make
print-PLIST</strong></span> command to output a PLIST
that matches any new files since the package was
extracted. See <a href="#build.helpful-targets" title=
"12.3. Other helpful targets">Section 12.3,
“Other helpful targets”</a> for more
information on this target.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"print-PLIST" id=
"print-PLIST"></a>9.3. Tweaking output of
<span><strong class="command">make
print-PLIST</strong></span></h2>
</div>
</div>
</div>
<p>If you have used any of the *-dirs packages, as
explained in <a href="#faq.common-dirs" title=
"9.8. Sharing directories between packages">Section 9.8,
“Sharing directories between packages”</a>,
you may have noticed that <span><strong class=
"command">make print-PLIST</strong></span> outputs a set
of <code class="varname">@comment</code>s instead of real
<code class="varname">@dirrm</code> lines. You can also
do this for specific directories and files, so that the
results of that command are very close to reality. This
helps <span class="emphasis"><em>a lot</em></span> during
the update of packages.</p>
<p>The <code class="varname">PRINT_PLIST_AWK</code>
variable takes a set of AWK patterns and actions that are
used to filter the output of print-PLIST. You can
<span class="emphasis"><em>append</em></span> any chunk
of AWK scripting you like to it, but be careful with
quoting.</p>
<p>For example, to get all files inside the <code class=
"filename">libdata/foo</code> directory removed from the
resulting PLIST:</p>
<pre class="programlisting">
PRINT_PLIST_AWK+= /^libdata\/foo/ { next; }
</pre>
<p>And to get all the <code class="varname">@dirrm</code>
lines referring to a specific (shared) directory
converted to <code class="varname">@comment</code>s:</p>
<pre class="programlisting">
PRINT_PLIST_AWK+= /^@dirrm share\/specific/ { print "@comment " $$0; next; }
</pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"plist.misc" id="plist.misc"></a>9.4. Variable
substitution in PLIST</h2>
</div>
</div>
</div>
<p>A number of variables are substituted automatically in
PLISTs when a package is installed on a system. This
includes the following variables:</p>
<div class="variablelist">
<dl>
<dt><span class="term"><code class=
"varname">${MACHINE_ARCH}</code>, <code class=
"varname">${MACHINE_GNU_ARCH}</code></span></dt>
<dd>
<p>Some packages like emacs and perl embed
information about which architecture they were
built on into the pathnames where they install
their file. To handle this case, PLIST will be
preprocessed before actually used, and the symbol
“<span class="quote"><code class=
"varname">${MACHINE_ARCH}</code></span>” will
be replaced by what <span><strong class=
"command">uname -p</strong></span> gives. The same
is done if the string <code class=
"varname">${MACHINE_GNU_ARCH}</code> is embedded in
PLIST somewhere - use this on packages that have
GNU autoconf created configure scripts.</p>
<div class="note" style=
"margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Legacy note</h3>
<p>There used to be a symbol “<span class=
"quote"><code class=
"varname">$ARCH</code></span>” that was
replaced by the output of <span><strong class=
"command">uname -m</strong></span>, but that's no
longer supported and has been removed.</p>
</div>
</dd>
<dt><span class="term"><code class=
"varname">${OPSYS}</code>, <code class=
"varname">${LOWER_OPSYS}</code>, <code class=
"varname">${OS_VERSION}</code></span></dt>
<dd>
<p>Some packages want to embed the OS name and
version into some paths. To do this, use these
variables in the <code class=
"filename">PLIST</code>:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><code class="varname">${OPSYS}</code> -
output of “<span class=
"quote"><span><strong class="command">uname
-s</strong></span></span>”</p>
</li>
<li>
<p><code class=
"varname">${LOWER_OPSYS}</code> - lowercase
common name (eg. “<span class=
"quote">solaris</span>”)</p>
</li>
<li>
<p><code class="varname">${OS_VERSION}</code>
- “<span class=
"quote"><span><strong class="command">uname
-r</strong></span></span>”</p>
</li>
</ul>
</div>
</dd>
<dt><span class="term"><code class=
"varname">${PKGLOCALEDIR}</code></span></dt>
<dd>
<p>Packages that install locale files should list
them in the PLIST as “<span class=
"quote">${PKGLOCALEDIR}/locale/de/LC_MESSAGES/...</span>”
instead of “<span class=
"quote">share/locale/de/LC_MESSAGES/...</span>”.
This properly handles the fact that different
operating systems expect locale files to be either
in <code class="filename">share</code> or
<code class="filename">lib</code> by default.</p>
</dd>
</dl>
</div>
<p>For a complete list of values which are replaced by
default, please look in <code class=
"filename">bsd.pkg.mk</code> (and search for <span class=
"emphasis"><em>PLIST_SUBST</em></span>).</p>
<p>If you want to change other variables not listed
above, you can add variables and their expansions to this
variable in the following way, similar to <code class=
"varname">MESSAGE_SUBST</code> (see <a href=
"#components.optional" title=
"7.5. Optional files">Section 7.5,
“Optional files”</a>):</p>
<pre class="programlisting">
PLIST_SUBST+= SOMEVAR="somevalue"
</pre>
<p>This replaces all occurrences of “<span class=
"quote">${SOMEVAR}</span>” in the PLIST with
“<span class="quote">somevalue</span>”.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"manpage-compression" id=
"manpage-compression"></a>9.5. Manpage-compression</h2>
</div>
</div>
</div>
<p>Manpages should be installed in compressed form if
<code class="varname">MANZ</code> is set (in <code class=
"filename">bsd.own.mk</code>), and uncompressed
otherwise. To handle this in the <code class=
"filename">PLIST</code> file, the suffix
“<span class="quote">.gz</span>” is
appended/removed automatically for manpages according to
<code class="varname">MANZ</code> and <code class=
"varname">MANCOMPRESSED</code> being set or not, see
above for details. This modification of the <code class=
"filename">PLIST</code> file is done on a copy of it, not
<code class="filename">PLIST</code> itself.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"using-PLIST_SRC" id=
"using-PLIST_SRC"></a>9.6. Changing PLIST
source with <code class=
"varname">PLIST_SRC</code></h2>
</div>
</div>
</div>
<p>To use one or more files as source for the
<code class="filename">PLIST</code> used in generating
the binary package, set the variable <code class=
"varname">PLIST_SRC</code> to the names of that file(s).
The files are later concatenated using <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?cat+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">cat</span>(1)</span></a>, and order of
things is important.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"platform-specific-plist" id=
"platform-specific-plist"></a>9.7. Platform
specific and differing PLISTs</h2>
</div>
</div>
</div>
<p>Some packages decide to install a different set of
files based on the operating system being used. These
differences can be automatically handled by using the
following files:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><code class="filename">PLIST.common</code></p>
</li>
<li>
<p><code class="filename">PLIST.${OPSYS}</code></p>
</li>
<li>
<p><code class=
"filename">PLIST.${MACHINE_ARCH}</code></p>
</li>
<li>
<p><code class=
"filename">PLIST.${OPSYS}-${MACHINE_ARCH}</code></p>
</li>
<li>
<p><code class=
"filename">PLIST.common_end</code></p>
</li>
</ul>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"faq.common-dirs" id=
"faq.common-dirs"></a>9.8. Sharing directories
between packages</h2>
</div>
</div>
</div>
<p>A “<span class="quote">shared
directory</span>” is a directory where multiple
(and unrelated) packages install files. These directories
are problematic because you have to add special tricks in
the PLIST to conditionally remove them, or have some
centralized package handle them.</p>
<p>Within pkgsrc, you'll find both approaches. If a
directory is shared by a few unrelated packages, it's
often not worth to add an extra package to remove it.
Therefore, one simply does:</p>
<pre class="programlisting">
@unexec ${RMDIR} %D/path/to/shared/directory 2>/dev/null || ${TRUE}
</pre>
<p>in the PLISTs of all affected packages, instead of the
regular "@dirrm" line.</p>
<p>However, if the directory is shared across many
packages, two different solutions are available:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>If the packages have a common dependency, the
directory can be removed in that. For example, see
<a xmlns="http://www.w3.org/TR/xhtml1/transitional"
href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/textproc/scrollkeeper/README.html"
class="pkgname">textproc/scrollkeeper</a>, which
removes the shared directory <code class=
"filename">share/omf</code>.</p>
</li>
<li>
<p>If the packages using the directory are not
related at all (they have no common dependencies),
a *-dirs package is used.</p>
</li>
</ol>
</div>
<p>From now on, we'll discuss the second solution. To get
an idea of the *-dirs packages available, issue:</p>
<pre class="programlisting">
<code class="prompt">%</code> cd .../pkgsrc
<code class="prompt">%</code> ls -d */*-dirs
</pre>
<p>Their use from other packages is very simple. The
<code class="varname">USE_DIRS</code> variable takes a
list of package names (without the “<span class=
"quote">-dirs</span>” part) together with the
required version number (always pick the latest one when
writting new packages).</p>
<p>For example, if a package installs files under
<code class="filename">share/applications</code>, it
should have the following line in it:</p>
<pre class="programlisting">
USE_DIRS+= xdg-1.1
</pre>
<p>After regenerating the PLIST using
<span><strong class="command">make
print-PLIST</strong></span>, you should get the right
(commented out) lines.</p>
<p>Note that, even if your package is using <code class=
"filename">$X11BASE</code>, it must not depend on the
*-x11-dirs packages. Just specify the name without that
part and pkgsrc (in particular, <code class=
"filename">mk/dirs.mk</code>) will take care of it.</p>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="buildlink" id=
"buildlink"></a>Chapter 10. Buildlink
methodology</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href=
"#converting-to-buildlink3">10.1. Converting packages
to use buildlink3</a></span></dt>
<dt><span class="sect1"><a href=
"#creating-buildlink3.mk">10.2. Writing <code class=
"filename">buildlink3.mk</code> files</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#anatomy-of-bl3">10.2.1. Anatomy of a
buildlink3.mk file</a></span></dt>
<dt><span class="sect2"><a href=
"#updating-buildlink-depends">10.2.2. Updating
<code class="varname">BUILDLINK_DEPENDS.<em class=
"replaceable"><code>pkg</code></em></code> in
<code class="filename">buildlink3.mk</code>
files</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#writing-builtin.mk">10.3. Writing <code class=
"filename">builtin.mk</code> files</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#anatomy-of-builtin.mk">10.3.1. Anatomy of a
<code class="filename">builtin.mk</code>
file</a></span></dt>
<dt><span class="sect2"><a href=
"#native-or-pkgsrc-preference">10.3.2. Global
preferences for native or pkgsrc
software</a></span></dt>
</dl>
</dd>
</dl>
</div>
<p>Buildlink is a framework in pkgsrc that controls what
headers and libraries are seen by a package's configure and
build processes. This is implemented in a two step
process:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>Symlink headers and libraries for dependencies
into <code class="varname">BUILDLINK_DIR</code>,
which by default is a subdirectory of <code class=
"varname">WRKDIR</code>.</p>
</li>
<li>
<p>Create wrapper scripts that are used in place of
the normal compiler tools that translate <code class=
"option">-I${LOCALBASE}/include</code> and
<code class="option">-L${LOCALBASE}/lib</code> into
references to <code class=
"varname">BUILDLINK_DIR</code>. The wrapper scripts
also make native compiler on some operating systems
look like GCC, so that packages that expect GCC won't
require modifications to build with those native
compilers.</p>
</li>
</ol>
</div>
<p>This normalizes the environment in which a package is
built so that the package may be built consistently despite
what other software may be installed. Please note that the
normal system header and library paths, e.g. <code class=
"filename">/usr/include</code>, <code class=
"filename">/usr/lib</code>, etc., are always searched --
buildlink3 is designed to insulate the package build from
non-system-supplied software.</p>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"converting-to-buildlink3" id=
"converting-to-buildlink3"></a>10.1. Converting
packages to use buildlink3</h2>
</div>
</div>
</div>
<p>The process of converting packages to use the
buildlink3 framework (“<span class=
"quote">bl3ifying</span>”) is fairly
straightforward. The things to keep in mind are:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>Ensure that the build always calls the wrapper
scripts instead of the actual toolchain. Some
packages are tricky, and the only way to know for
sure is the check <code class=
"filename">${WRKDIR}/.work.log</code> to see if the
wrappers are being invoked.</p>
</li>
<li>
<p>Don't override <code class=
"varname">PREFIX</code> from within the package
Makefile, e.g. Java VMs, standalone shells, etc.,
because the code to symlink files into <code class=
"filename">${BUILDLINK_DIR}</code> looks for files
relative to “<span class="quote">pkg_info -qp
<em class=
"replaceable"><code>pkgname</code></em></span>”.</p>
</li>
<li>
<p>Remember that <span class=
"emphasis"><em>only</em></span> the <code class=
"filename">buildlink3.mk</code> files that you list
in a package's Makefile are added as dependencies
for that package.</p>
</li>
</ol>
</div>
<p>If a dependency on a particular package is required
for its libraries and headers, then we replace:</p>
<pre class="programlisting">
DEPENDS+= foo>=1.1.0:../../category/foo
</pre>
<p>with</p>
<pre class="programlisting">
.include "../../category/foo/buildlink3.mk"
</pre>
<p>There are several <code class=
"filename">buildlink3.mk</code> files in <code class=
"filename">pkgsrc/mk</code> that handle special package
issues:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><code class="filename">bdb.buildlink3.mk</code>
chooses either the native or a pkgsrc Berkeley DB
implementation based on the values of <code class=
"varname">BDB_ACCEPTED</code> and <code class=
"varname">BDB_DEFAULT</code>.</p>
</li>
<li>
<p><code class=
"filename">curses.buildlink3.mk</code> If the
system comes with neither Curses nor NCurses, this
will take care to install the <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/ncurses/README.html"
class="pkgname">devel/ncurses</a> package.</p>
</li>
<li>
<p><code class="filename">krb5.buildlink3.mk</code>
uses the value of <code class=
"varname">KRB5_ACCEPTED</code> to choose between
adding a dependency on Heimdal or MIT-krb5 for
packages that require a Kerberos 5
implementation.</p>
</li>
<li>
<p><code class=
"filename">motif.buildlink3.mk</code> checks for a
system-provided Motif installation or adds a
dependency on <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/lesstif/README.html"
class="pkgname">x11/lesstif</a> or <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/openmotif/README.html"
class="pkgname">x11/openmotif</a>;</p>
</li>
<li>
<p><code class=
"filename">ossaudio.buildlink3.mk</code> defines
several variables that may be used by packages that
use the Open Sound System (OSS) API;</p>
</li>
<li>
<p><code class=
"filename">pgsql.buildlink3.mk</code> will accept
either Postgres 7.3 or 7.4, whichever is found
installed. See the file for more information.</p>
</li>
<li>
<p><code class=
"filename">pthread.buildlink3.mk</code> uses the
value of <code class="varname">PTHREAD_OPTS</code>
and checks for native pthreads or adds a dependency
on <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/pth/README.html"
class="pkgname">devel/pth</a> as needed;</p>
</li>
<li>
<p><code class="filename">xaw.buildlink3.mk</code>
uses the value of <code class=
"varname">XAW_TYPE</code> to choose a particular
Athena widgets library.</p>
</li>
</ul>
</div>
<p>The comments in those <code class=
"filename">buildlink3.mk</code> files provide a more
complete description of how to use them properly.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"creating-buildlink3.mk" id=
"creating-buildlink3.mk"></a>10.2. Writing
<code class="filename">buildlink3.mk</code>
files</h2>
</div>
</div>
</div>
<p>A package's <code class=
"filename">buildlink3.mk</code> file is included by
Makefiles to indicate the need to compile and link
against header files and libraries provided by the
package. A <code class="filename">buildlink3.mk</code>
file should always provide enough information to add the
correct type of dependency relationship and include any
other <code class="filename">buildlink3.mk</code> files
that it needs to find headers and libraries that it needs
in turn.</p>
<p>To generate an initial <code class=
"filename">buildlink3.mk</code> file for further editing,
Rene Hexel's <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/createbuildlink/README.html"
class="pkgname">pkgtools/createbuildlink</a> package is
highly recommended. For most packages, the following
command will generate a good starting point for
<code class="filename">buildlink3.mk</code> files:</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>cd pkgsrc/<em class=
"replaceable"><code>category</code></em>/<em class=
"replaceable"><code>pkgdir</code></em>
<code class=
"prompt">%</code> createbuildlink -3 >buildlink3.mk</code></strong>
</pre>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="anatomy-of-bl3" id=
"anatomy-of-bl3"></a>10.2.1. Anatomy of a
buildlink3.mk file</h3>
</div>
</div>
</div>
<p>The following real-life example <code class=
"filename">buildlink3.mk</code> is taken from
<code class="filename">pkgsrc/graphics/tiff</code>:</p>
<pre class="programlisting">
# $NetBSD: buildlink3.mk,v 1.7 2004/03/18 09:12:12 jlam Exp $
BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH}+
TIFF_BUILDLINK3_MK:= ${TIFF_BUILDLINK3_MK}+
.if !empty(BUILDLINK_DEPTH:M+)
BUILDLINK_DEPENDS+= tiff
.endif
BUILDLINK_PACKAGES:= ${BUILDLINK_PACKAGES:Ntiff}
BUILDLINK_PACKAGES+= tiff
.if !empty(TIFF_BUILDLINK3_MK:M+)
BUILDLINK_DEPENDS.tiff+= tiff>=3.6.1
BUILDLINK_PKGSRCDIR.tiff?= ../../graphics/tiff
.endif # TIFF_BUILDLINK3_MK
.include "../../devel/zlib/buildlink3.mk"
.include "../../graphics/jpeg/buildlink3.mk"
BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH:S/+$//}
</pre>
<p>The header and footer manipulate <code class=
"varname">BUILDLINK_DEPTH</code>, which is common
across all <code class="filename">buildlink3.mk</code>
files and is used to track at what depth we are
including <code class="filename">buildlink3.mk</code>
files.</p>
<p>The first section controls if the dependency on
<em class="replaceable"><code>pkg</code></em> is added.
<code class="varname">BUILDLINK_DEPENDS</code> is the
global list of packages for which dependencies are
added by buildlink3.</p>
<p>The second section advises pkgsrc that the
<code class="filename">buildlink3.mk</code> file for
<em class="replaceable"><code>pkg</code></em> has been
included at some point. <code class=
"varname">BUILDLINK_PACKAGES</code> is the global list
of packages for which <code class=
"filename">buildlink3.mk</code> files have been
included. It must <span class=
"emphasis"><em>always</em></span> be appended to within
a <code class="filename">buildlink3.mk</code> file.</p>
<p>The third section is protected from multiple
inclusion and controls how the dependency on <em class=
"replaceable"><code>pkg</code></em> is added. Several
important variables are set in the section:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><code class=
"varname">BUILDLINK_DEPENDS.<em class=
"replaceable"><code>pkg</code></em></code> is the
actual dependency recorded in the installed
package; this should always be set using
<span><strong class="command">+=</strong></span>
to ensure that we're appending to any
pre-existing list of values. This variable should
be set to the first version of the package that
had the last change in the major number of a
shared library or that had a major API
change.</p>
</li>
<li>
<p><code class=
"varname">BUILDLINK_PKGSRCDIR.<em class=
"replaceable"><code>pkg</code></em></code> is the
location of the <em class=
"replaceable"><code>pkg</code></em> pkgsrc
directory;</p>
</li>
<li>
<p><code class=
"varname">BUILDLINK_DEPMETHOD.<em class=
"replaceable"><code>pkg</code></em></code> (not
shown above) controls whether we use <code class=
"varname">BUILD_DEPENDS</code> or <code class=
"varname">DEPENDS</code> to add the dependency on
<em class="replaceable"><code>pkg</code></em>.
The build dependency is selected by setting
<code class=
"varname">BUILDLINK_DEPMETHOD.<em class=
"replaceable"><code>pkg</code></em></code> to
“<span class="quote">build</span>”.
By default, the full dependency is used.</p>
</li>
<li>
<p><code class=
"varname">BUILDLINK_INCDIRS.<em class=
"replaceable"><code>pkg</code></em></code> and
<code class=
"varname">BUILDLINK_LIBDIRS.<em class="replaceable">
<code>pkg</code></em></code> (not shown above)
are lists of subdirectories of <code class=
"filename">${BUILDLINK_PREFIX.<em class=
"replaceable"><code>pkg</code></em>}</code> to
add to the header and library search paths. These
default to “<span class=
"quote">include</span>” and
“<span class="quote">lib</span>”
respectively.</p>
</li>
<li>
<p><code class=
"varname">BUILDLINK_CPPFLAGS.<em class=
"replaceable"><code>pkg</code></em></code> (not
shown above) is the list of preprocessor flags to
add to <code class="varname">CPPFLAGS</code>,
which are passed on to the configure and build
phases. The “<span class=
"quote">-I</span>” option should be avoided
and instead be handled using <code class=
"varname">BUILDLINK_INCDIRS.<em class=
"replaceable"><code>pkg</code></em></code> as
above.</p>
</li>
</ul>
</div>
<p>The following variables are all optionally defined
within this second section (protected against multiple
inclusion) and control which package files are
symlinked into <code class=
"filename">${BUILDLINK_DIR}</code> and how their names
are transformed during the symlinking:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><code class=
"varname">BUILDLINK_FILES.<em class=
"replaceable"><code>pkg</code></em></code> (not
shown above) is a shell glob pattern relative to
<code class=
"filename">${BUILDLINK_PREFIX.<em class=
"replaceable"><code>pkg</code></em>}</code> to be
symlinked into <code class=
"filename">${BUILDLINK_DIR}</code>, e.g.
<code class="filename">include/*.h</code>.</p>
</li>
<li>
<p><code class=
"varname">BUILDLINK_FILES_CMD.<em class=
"replaceable"><code>pkg</code></em></code> (not
shown above) is a shell pipeline that outputs to
stdout a list of files relative to <code class=
"filename">${BUILDLINK_PREFIX.<em class=
"replaceable"><code>pkg</code></em>}</code>. The
resulting files are to be symlinked into
<code class="filename">${BUILDLINK_DIR}</code>.
By default, this takes the <code class=
"filename">+CONTENTS</code> of a <em class=
"replaceable"><code>pkg</code></em> and filters
it through <code class=
"varname">${BUILDLINK_CONTENTS_FILTER.<em class=
"replaceable"><code>pkg</code></em>}</code>.</p>
</li>
<li>
<p><code class=
"varname">BUILDLINK_CONTENTS_FILTER.<em class=
"replaceable"><code>pkg</code></em></code> (not
shown above) is a filter command that filters
<code class="filename">+CONTENTS</code> input
into a list of files relative to <code class=
"filename">${BUILDLINK_PREFIX.<em class=
"replaceable"><code>pkg</code></em>}</code> on
stdout. By default for overwrite packages,
<code class=
"varname">BUILDLINK_CONTENTS_FILTER.<em class=
"replaceable"><code>pkg</code></em></code>
outputs the contents of the <code class=
"filename">include</code> and <code class=
"filename">lib</code> directories in the package
<code class="filename">+CONTENTS</code>, and for
pkgviews packages, it outputs any libtool
archives in <code class="filename">lib</code>
directories.</p>
</li>
<li>
<p><code class=
"varname">BUILDLINK_TRANSFORM.<em class=
"replaceable"><code>pkg</code></em></code> (not
shown above) is a list of sed arguments used to
transform the name of the source filename into a
destination filename, e.g. <span><strong class=
"command">-e
"s|/curses.h|/ncurses.h|g"</strong></span>.</p>
</li>
</ul>
</div>
<p>The last section includes any <code class=
"filename">buildlink3.mk</code> needed for <em class=
"replaceable"><code>pkg</code></em>'s library
dependencies. Including these <code class=
"filename">buildlink3.mk</code> files means that the
headers and libraries for these dependencies are also
symlinked into <code class=
"filename">${BUILDLINK_DIR}</code> whenever the
<em class="replaceable"><code>pkg</code></em>
<code class="filename">buildlink3.mk</code> file is
included.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"updating-buildlink-depends" id=
"updating-buildlink-depends"></a>10.2.2. Updating
<code class=
"varname">BUILDLINK_DEPENDS.<em class="replaceable">
<code>pkg</code></em></code> in <code class=
"filename">buildlink3.mk</code> files</h3>
</div>
</div>
</div>
<p>There are two situations that require increasing the
dependency listed in <code class=
"varname">BUILDLINK_DEPENDS.<em class=
"replaceable"><code>pkg</code></em></code> after a
package update:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>if the sonames (major number of the library
version) of any installed shared libraries
change;</p>
</li>
<li>
<p>if the API or interface to the header files
change.</p>
</li>
</ol>
</div>
<p>In these cases, <code class=
"varname">BUILDLINK_DEPENDS.<em class=
"replaceable"><code>pkg</code></em></code> should be
adjusted to require at least the new package version.
In some cases, the packages that depend on this new
version may need their <code class=
"varname">PKGREVISION</code>s increased and, if they
have <code class="filename">buildlink3.mk</code> files,
their <code class=
"varname">BUILDLINK_DEPENDS.<em class="replaceable"><code>
pkg</code></em></code> adjusted, too. This is needed so
that binary packages made using it will require the
correct package dependency and not settle for an older
one which will not contain the necessary shared
libraries.</p>
<p>Please take careful consideration before adjusting
<code class="varname">BUILDLINK_DEPENDS.<em class=
"replaceable"><code>pkg</code></em></code> as we don't
want to cause unneeded package deletions and rebuilds.
In many cases, new versions of packages work just fine
with older dependencies. See <a href="#dependencies"
title="13.1.4. Handling dependencies">Section
13.1.4, “Handling dependencies”</a> and
<a href="#buildlink" title=
"Chapter 10. Buildlink methodology">Chapter
10, <i>Buildlink methodology</i></a> for more
information about dependencies on other packages,
including the <code class=
"varname">BUILDLINK_RECOMMENDED</code> and <code class=
"varname">RECOMMENDED</code> definitions.</p>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"writing-builtin.mk" id=
"writing-builtin.mk"></a>10.3. Writing
<code class="filename">builtin.mk</code> files</h2>
</div>
</div>
</div>
<p>Some packages in pkgsrc install headers and libraries
that coincide with headers and libraries present in the
base system. Aside from a <code class=
"filename">buildlink3.mk</code> file, these packages
should also include a <code class=
"filename">builtin.mk</code> file that includes the
necessary checks to decide whether using the built-in
software or the pkgsrc software is appropriate.</p>
<p>The only requirements of a builtin.mk file for
<em class="replaceable"><code>pkg</code></em> are:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>It should set <code class=
"varname">USE_BUILTIN.<em class=
"replaceable"><code>pkg</code></em></code> to
either “<span class="quote">yes</span>”
or “<span class="quote">no</span>”
after it is included.</p>
</li>
<li>
<p>It should <span class=
"emphasis"><em>not</em></span> override any
<code class="varname">USE_BUILTIN.<em class=
"replaceable"><code>pkg</code></em></code> which is
already set before the <code class=
"filename">builtin.mk</code> file is included.</p>
</li>
<li>
<p>It should be written to allow multiple
inclusion. This is <span class=
"emphasis"><em>very</em></span> important and takes
careful attention to <code class=
"filename">Makefile</code> coding.</p>
</li>
</ol>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="anatomy-of-builtin.mk"
id=
"anatomy-of-builtin.mk"></a>10.3.1. Anatomy
of a <code class="filename">builtin.mk</code>
file</h3>
</div>
</div>
</div>
<p>The following is the recommended template for
builtin.mk files:</p>
<pre class="programlisting">
.if !defined(IS_BUILTIN.foo)
#
# IS_BUILTIN.foo is set to "yes" or "no" depending on whether "foo"
# genuinely exists in the system or not.
#
IS_BUILTIN.foo?= no
# BUILTIN_PKG.foo should be set here if "foo" is built-in and its package
# version can be determined.
#
. if !empty(IS_BUILTIN.foo:M[yY][eE][sS])
BUILTIN_PKG.foo?= foo-1.0
. endif
.endif # IS_BUILTIN.foo
.if !defined(USE_BUILTIN.foo)
USE_BUILTIN.foo?= ${IS_BUILTIN.foo}
. if defined(BUILTIN_PKG.foo)
. for _depend_ in ${BUILDLINK_DEPENDS.foo}
. if !empty(USE_BUILTIN.foo:M[yY][eE][sS])
USE_BUILTIN.foo!= \
if ${PKG_ADMIN} pmatch '${_depend_}' ${BUILTIN_PKG.foo}; then \
${ECHO} "yes"; \
else \
${ECHO} "no"; \
fi
. endif
. endfor
. endif
.endif # USE_BUILTIN.foo
CHECK_BUILTIN.foo?= no
.if !empty(CHECK_BUILTIN.foo:M[nN][oO])
#
# Here we place code that depends on whether USE_BUILTIN.foo is set to
# "yes" or "no".
#
.endif # CHECK_BUILTIN.foo
</pre>
<p>The first section sets <code class=
"varname">IS_BUILTIN.<em class=
"replaceable"><code>pkg</code></em></code> depending on
if <em class="replaceable"><code>pkg</code></em> really
exists in the base system. This should not be a base
system software with similar functionality to
<em class="replaceable"><code>pkg</code></em>; it
should only be “<span class=
"quote">yes</span>” if the actual package is
included as part of the base system. This variable is
only used internally within the <code class=
"filename">builtin.mk</code> file.</p>
<p>The second section sets <code class=
"varname">BUILTIN_PKG.<em class=
"replaceable"><code>pkg</code></em></code> to the
version of <em class=
"replaceable"><code>pkg</code></em> in the base system
if it exists (if <code class=
"varname">IS_BUILTIN.<em class=
"replaceable"><code>pkg</code></em></code> is
“<span class="quote">yes</span>”). This
variable is only used internally within the
<code class="filename">builtin.mk</code> file.</p>
<p>The third section sets <code class=
"varname">USE_BUILTIN.<em class=
"replaceable"><code>pkg</code></em></code> and is
<span class="emphasis"><em>required</em></span> in all
<code class="filename">builtin.mk</code> files. The
code in this section must make the determination
whether the built-in software is adequate to satisfy
the dependencies listed in <code class=
"varname">BUILDLINK_DEPENDS.<em class=
"replaceable"><code>pkg</code></em></code>. This is
typically done by comparing <code class=
"varname">BUILTIN_PKG.<em class=
"replaceable"><code>pkg</code></em></code> against each
of the dependencies in <code class=
"varname">BUILDLINK_DEPENDS.<em class=
"replaceable"><code>pkg</code></em></code>.
<code class="varname">USE_BUILTIN.<em class=
"replaceable"><code>pkg</code></em></code> <span class=
"emphasis"><em>must</em></span> be set to the correct
value by the end of the <code class=
"filename">builtin.mk</code> file. Note that
<code class="varname">USE_BUILTIN.<em class=
"replaceable"><code>pkg</code></em></code> may be
“<span class="quote">yes</span>” even if
<code class="varname">IS_BUILTIN.<em class=
"replaceable"><code>pkg</code></em></code> is
“<span class="quote">no</span>” because we
may make the determination that the built-in version of
the software is similar enough to be used as a
replacement.</p>
<p>The last section is guarded by <code class=
"varname">CHECK_BUILTIN.<em class=
"replaceable"><code>pkg</code></em></code>, and
includes code that uses the value of <code class=
"varname">USE_BUILTIN.<em class=
"replaceable"><code>pkg</code></em></code> set in the
previous section. This typically includes, e.g., adding
additional dependency restrictions and listing
additional files to symlink into <code class=
"filename">${BUILDLINK_DIR}</code> (via <code class=
"varname">BUILDLINK_FILES.<em class=
"replaceable"><code>pkg</code></em></code>).</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"native-or-pkgsrc-preference" id=
"native-or-pkgsrc-preference"></a>10.3.2. Global
preferences for native or pkgsrc software</h3>
</div>
</div>
</div>
<p>When building packages, it's possible to choose
whether to set a global preference for using either the
built-in (native) version or the pkgsrc version of
software to satisfy a dependency. This is controlled by
setting <code class="varname">PREFER_PKGSRC</code> and
<code class="varname">PREFER_NATIVE</code>. These
variables take values of either “<span class=
"quote">yes</span>”, “<span class=
"quote">no</span>”, or a list of packages.
<code class="varname">PREFER_PKGSRC</code> tells pkgsrc
to use the pkgsrc versions of software, while
<code class="varname">PREFER_NATIVE</code> tells pkgsrc
to use the built-in versions. Preferences are
determined by the most specific instance of the package
in either <code class="varname">PREFER_PKGSRC</code> or
<code class="varname">PREFER_NATIVE</code>. If a
package is specified in neither or in both variables,
then <code class="varname">PREFER_PKGSRC</code> has
precedence over <code class=
"varname">PREFER_NATIVE</code>. For example, to require
using pkgsrc versions of software for all but the most
basic bits on a NetBSD system, you can set:</p>
<pre class="programlisting">
PREFER_PKGSRC= yes
PREFER_NATIVE= getopt skey tcp_wrappers
</pre>
<p>A package <span class=
"emphasis"><em>must</em></span> have a <code class=
"filename">builtin.mk</code> file to be listed in
<code class="varname">PREFER_NATIVE</code>, otherwise
it is simply ignored in that list.</p>
</div>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="options" id=
"options"></a>Chapter 11. Options
handling</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href=
"#global-default-options">11.1. Global default
options</a></span></dt>
<dt><span class="sect1"><a href=
"#converting-to-options">11.2. Converting packages to
use <code class=
"filename">bsd.options.mk</code></a></span></dt>
</dl>
</div>
<p>Many packages have the ability to be built to support
different sets of features. <code class=
"filename">bsd.options.mk</code> is a framework in pkgsrc
that provides generic handling of those options that
determine different ways in which the packages can be
built. It's possible for the user to specify exactly which
sets of options will be built into a package or to allow a
set of global default options apply.</p>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"global-default-options" id=
"global-default-options"></a>11.1. Global
default options</h2>
</div>
</div>
</div>
<p>Global default options are listed in <code class=
"varname">PKG_DEFAULT_OPTIONS</code>, which is a list of
the options that should be built into every package if
that option is supported. This variable should be set in
<code class="filename">/etc/mk.conf</code>.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"converting-to-options" id=
"converting-to-options"></a>11.2. Converting
packages to use <code class=
"filename">bsd.options.mk</code></h2>
</div>
</div>
</div>
<p>The following example shows how <code class=
"filename">bsd.options.mk</code> should be used by the
hypothetical ``wibble'' package, either in the package
<code class="filename">Makefile</code>, or in a file,
e.g. <code class="filename">options.mk</code>, that is
included by the main package <code class=
"filename">Makefile</code>.</p>
<pre class="programlisting">
# Global and legacy options
PKG_OPTIONS_VAR= PKG_OPTIONS.wibble
PKG_SUPPORTED_OPTIONS= ldap sasl
PKG_SUGGESTED_OPTIONS= sasl
PKG_OPTION_LEGACY_VARS= WIBBLE_USE_OPENLDAP:ldap USE_SASL2:sasl
.include "../../mk/bsd.options.mk"
# Package-specific option-handling
###
### LDAP support
###
.if !empty(PKG_OPTIONS:Mldap)
. include "../../databases/openldap/buildlink3.mk"
CONFIGURE_ARGS+= --enable-ldap=${BUILDLINK_PREFIX.openldap}
.endif
###
### SASL authentication
###
.if !empty(PKG_OPTIONS:Msasl)
. include "../../security/cyrus-sasl2/buildlink3.mk"
CONFIGURE_ARGS+= --enable-sasl=${BUILDLINK_PREFIX.sasl}
.endif
</pre>
<p>The first section contains the information about which
build options are supported by the package, and any
default options settings if needed.</p>
<div class="orderedlist">
<ol type="1">
<li>
<p><code class="varname">PKG_OPTIONS_VAR</code> is
the name of the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">make</span>(1)</span></a> variable
that contains the options the user wishes to
select. The recommended value is
“<span class="quote">PKG_OPTIONS.<em class=
"replaceable"><code>pkg</code></em></span>”
but any package-specific value may be used. This
variable should be set in a package Makefile.</p>
</li>
<li>
<p><code class=
"varname">PKG_SUPPORTED_OPTIONS</code> is a list of
build options supported by the package. This
variable should be set in a package Makefile.</p>
</li>
<li>
<p><code class=
"varname">PKG_SUGGESTED_OPTIONS</code> is a list of
build options which are enabled by default.</p>
</li>
<li>
<p><code class="varname">${PKG_OPTIONS_VAR}</code>
(the variable named in <code class=
"varname">PKG_OPTIONS_VAR</code>) lists the
selected build options and overrides any default
options given in <code class=
"varname">PKG_DEFAULT_OPTIONS</code>. If any of the
options begin with a “<span class=
"quote">-</span>”, then that option is always
removed from the selected build options, e.g.</p>
<pre class="programlisting">
PKG_DEFAULT_OPTIONS= kerberos ldap sasl
PKG_OPTIONS_VAR= WIBBLE_OPTIONS
WIBBLE_OPTIONS= ${PKG_DEFAULT_OPTIONS} -sasl
# leads to PKG_OPTIONS = kerberos ldap
</pre>
<p>or</p>
<pre class="programlisting">
PKG_OPTIONS_VAR= WIBBLE_OPTIONS
WIBBLE_OPTIONS= kerberos -ldap ldap
# leads to PKG_OPTIONS = kerberos
</pre>
<p>This variable should be set in <code class=
"filename">/etc/mk.conf</code>.</p>
</li>
<li>
<p>The <code class=
"varname">PKG_OPTIONS_LEGACY_VARS</code> is only
needed if you are converting a package that had its
own ad-hoc options handling to use <code class=
"filename">bsd.options.mk</code>. It converts
global or legacy options variables into an
equivalent <code class=
"varname">PKG_OPTIONS.<em class=
"replaceable"><code>pkg</code></em></code>
value.</p>
</li>
</ol>
</div>
<p>After the inclusion of bsd.options.mk, the variable
<code class="varname">PKG_OPTIONS</code> contains the
list of the selected build options, properly filtered to
remove unsupported and duplicate options.</p>
<p>The remaining sections contain the logic that is
specific to each option. There should be a check for
every option listed in <code class=
"varname">PKG_SUPPORTED_OPTIONS</code>, and there should
be clear documentation on what turning on the option will
do in the comments preceding each section. The correct
way to check for an option is to check whether it is
listed in <code class="varname">PKG_OPTIONS</code>.</p>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="build" id=
"build"></a>Chapter 12. The build
process</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href="#build.prefix">12.1.
Program location</a></span></dt>
<dt><span class="sect1"><a href="#main-targets">12.2.
Main targets</a></span></dt>
<dt><span class="sect1"><a href=
"#build.helpful-targets">12.3. Other helpful
targets</a></span></dt>
</dl>
</div>
<p>The basic steps for building a program are always the
same. First the program's source (<span class=
"emphasis"><em>distfile</em></span>) must be brought to the
local system and then extracted. After any patches to
compile properly on NetBSD are applied, the software can be
configured, then built (usually by compiling), and finally
the generated binaries, etc. can be put into place on the
system. These are exactly the steps performed by the NetBSD
package system, which is implemented as a series of targets
in a central Makefile, <code class=
"filename">pkgsrc/mk/bsd.pkg.mk</code>.</p>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"build.prefix" id=
"build.prefix"></a>12.1. Program location</h2>
</div>
</div>
</div>
<p>Before outlining the process performed by the NetBSD
package system in the next section, here's a brief
discussion on where programs are installed, and which
variables influence this.</p>
<p>The automatic variable <code class=
"varname">PREFIX</code> indicates where all files of the
final program shall be installed. It is usually set to
<code class="varname">LOCALBASE</code> (<code class=
"filename">/usr/pkg</code>), or <code class=
"varname">CROSSBASE</code> for pkgs in the
“<span class="quote">cross</span>” category.
The value of <code class="varname">PREFIX</code> needs to
be put into the various places in the program's source
where paths to these files are encoded. See <a href=
"#components.patches" title=
"7.3. patches/*">Section 7.3,
“patches/*”</a> and <a href="#fixes.libtool"
title=
"13.3.1. Shared libraries - libtool">Section 13.3.1,
“Shared libraries - libtool”</a> for more
details.</p>
<p>When choosing which of these variables to use, follow
the following rules:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><code class="varname">PREFIX</code> always
points to the location where the current pkg will
be installed. When referring to a pkg's own
installation path, use “<span class=
"quote">${PREFIX}</span>”.</p>
</li>
<li>
<p><code class="varname">LOCALBASE</code> is where
all non-X11 pkgs are installed. If you need to
construct a -I or -L argument to the compiler to
find includes and libraries installed by another
non-X11 pkg, use “<span class=
"quote">${LOCALBASE}</span>”.</p>
</li>
<li>
<p><code class="varname">X11BASE</code> is where
the actual X11 distribution (from xsrc, etc.) is
installed. When looking for <span class=
"emphasis"><em>standard</em></span> X11 includes
(not those installed by a pkg), use
“<span class=
"quote">${X11BASE}</span>”.</p>
</li>
<li>
<p>X11 based are special in that they may be
installed in either <code class=
"varname">X11BASE</code> or <code class=
"varname">LOCALBASE</code>.</p>
<p>Usually, X11 packages should be installed under
<code class="varname">LOCALBASE</code> whenever
possible. Note that you will need to set
<code class="varname">USE_X11</code> in them to
request the presence of X11 and to get the right
compilation flags.</p>
<p>Even though, there are some packages that cannot
be installed under <code class=
"varname">LOCALBASE</code>: those that come with
app-defaults files. These packages are special and
they must be placed under <code class=
"varname">X11BASE</code>. To accomplish this, set
either <code class="varname">USE_X11BASE</code> or
<code class="varname">USE_IMAKE</code> in your
package.</p>
<p>Some notes: <code class="varname">USE_X11</code>
and <code class="varname">USE_X11BASE</code> are
mutually exclusive. If you need to find includes or
libraries installed by a pkg that has <code class=
"varname">USE_IMAKE</code> or <code class=
"varname">USE_X11BASE</code> in its pkg
<code class="filename">Makefile</code>, you need to
use <span class="emphasis"><em>both</em></span>
<code class="filename">${X11BASE}</code> and
<code class="filename">${LOCALBASE}</code>. To
force installation of all X11 packages in
<code class="varname">LOCALBASE</code>, the
<a xmlns="http://www.w3.org/TR/xhtml1/transitional"
href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/xpkgwedge/README.html"
class="pkgname">pkgtools/xpkgwedge</a> is enabled
by default.</p>
</li>
<li>
<p><code class="varname">X11PREFIX</code> should be
used to refer to the installed location of an X11
package. <code class="varname">X11PREFIX</code>
will be set to <code class="varname">X11BASE</code>
if xpkgwedge is not installed, and to <code class=
"varname">LOCALBASE</code> if xpkgwedge is
installed.</p>
</li>
<li>
<p>If xpkgwedge is installed, it is possible to
have some packages installed in <code class=
"varname">X11BASE</code> and some in <code class=
"varname">LOCALBASE</code>. To determine the prefix
of an installed package, the <code class=
"varname">EVAL_PREFIX</code> definition can be
used. It takes pairs in the format
“<span class=
"quote">DIRNAME=<package></span>”, and
the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">make</span>(1)</span></a> variable
<code class="varname">DIRNAME</code> will be set to
the prefix of the installed package
<package>, or “<span class=
"quote">${X11PREFIX}</span>” if the package
is not installed.</p>
<p>This is best illustrated by example.</p>
<p>The following lines are taken from <code class=
"filename">pkgsrc/wm/scwm/Makefile</code>:</p>
<pre class="programlisting">
EVAL_PREFIX+= GTKDIR=gtk+
CONFIGURE_ARGS+= --with-guile-prefix=${LOCALBASE} \
--with-gtk-prefix="${GTKDIR}" \
--enable-multibyte
</pre>
<p>Specific defaults can be defined for the
packages evaluated using <code class=
"varname">EVAL_PREFIX</code>, by using a definition
of the form:</p>
<pre class="programlisting">
GTKDIR_DEFAULT= ${LOCALBASE}
</pre>
<p>where <code class="varname">GTKDIR</code>
corresponds to the first definition in the
<code class="varname">EVAL_PREFIX</code> pair.</p>
</li>
<li>
<p>Within <code class="filename">${PREFIX}</code>,
packages should install files according to <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?hier+7+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">hier</span>(7)</span></a>, with the
exception that manual pages go into <code class=
"filename">${PREFIX}/man</code>, not <code class=
"filename">${PREFIX}/share/man</code>.</p>
</li>
</ul>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"main-targets" id=
"main-targets"></a>12.2. Main targets</h2>
</div>
</div>
</div>
<p>The main targets used during the build process defined
in <code class="filename">bsd.pkg.mk</code> are:</p>
<div class="variablelist">
<dl>
<dt><span class="term">fetch</span></dt>
<dd>
<p>This will check if the file(s) given in the
variables <code class="varname">DISTFILES</code>
and <code class="varname">PATCHFILES</code> (as
defined in the package's Makefile) are present on
the local system in <code class=
"filename">/usr/pkgsrc/distfiles</code>. If they
are not present, an attempt will be made to fetch
them using commands of the form:</p>
<pre class="programlisting">
${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS}
</pre>
<p>where ${site} varies through several
possibilities in turn: first, <code class=
"varname">MASTER_SITE_OVERRIDE</code> is tried,
then the sites specified in either <code class=
"varname">SITES_file</code> if defined, else
<code class="varname">MASTER_SITES</code> or
<code class="varname">PATCH_SITES</code>, as
applies, then finally the value of <code class=
"varname">MASTER_SITE_BACKUP</code>. The order of
all except the first can be optionally sorted by
the user, via setting either <code class=
"varname">MASTER_SORT_AWK</code> or <code class=
"varname">MASTER_SORT_REGEX</code>.</p>
</dd>
<dt><span class="term">checksum</span></dt>
<dd>
<p>After the distfile(s) are fetched, their
checksum is generated and compared with the
checksums stored in the distinfo file. If the
checksums don't match, the build is aborted. This
is to ensure the same distfile is used for
building, and that the distfile wasn't changed,
e.g. by some malign force, deliberately changed
distfiles on the master distribution site or
network lossage.</p>
</dd>
<dt><span class="term">extract</span></dt>
<dd>
<p>When the distfiles are present on the local
system, they need to be extracted, as they are
usually in the form of some compressed archive
format, most commonly <code class=
"filename">.tar.gz</code>.</p>
<p>If only some of the distfiles need to be
uncompressed, the files to be uncompressed should
be put into <code class=
"varname">EXTRACT_ONLY</code>.</p>
<p>If the distfiles are not in <code class=
"filename">.tar.gz</code> format, they can be
extracted by setting either <code class=
"varname">EXTRACT_SUFX</code>, or <code class=
"varname">EXTRACT_CMD</code>, <code class=
"varname">EXTRACT_BEFORE_ARGS</code> and
<code class="varname">EXTRACT_AFTER_ARGS</code>. In
the former case, pkgsrc knows how to extract a
number of suffixes (<code class=
"filename">.tar.gz</code>, <code class=
"filename">.tgz</code>, <code class=
"filename">.tar.gz2</code>, <code class=
"filename">.tbz</code>, <code class=
"filename">.tar.Z</code>, <code class=
"filename">.tar</code>, <code class=
"filename">.shar.gz</code>, <code class=
"filename">.shar.bz2</code>, <code class=
"filename">.shar.Z</code>, <code class=
"filename">.shar</code>, <code class=
"filename">.Z</code>, <code class=
"filename">.bz2</code> and <code class=
"filename">.gz</code>; see the definition of the
various <code class="varname">DECOMPRESS_CMD</code>
variables <code class="filename">bsd.pkg.mk</code>
for a complete list). Here's an example on how to
use the other variables for a program that comes
with a compressed shell archive whose name ends in
<code class="filename">.msg.gz</code>:</p>
<pre class="programlisting">
EXTRACT_SUFX= .msg.gz
EXTRACT_CMD= zcat
EXTRACT_BEFORE_ARGS=
EXTRACT_AFTER_ARGS= |sh
</pre>
</dd>
<dt><span class="term">patch</span></dt>
<dd>
<p>After extraction, all the patches named by the
<code class="varname">PATCHFILES</code>, those
present in the patches subdirectory of the package
as well as in $LOCALPATCHES/$PKGPATH (e.g.
<code class=
"filename">/usr/local/patches/graphics/png</code>)
are applied. Patchfiles ending in <code class=
"filename">.Z</code> or <code class=
"filename">.gz</code> are uncompressed before they
are applied, files ending in <code class=
"filename">.orig</code> or <code class=
"filename">.rej</code> are ignored. Any special
options to <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?patch+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">patch</span>(1)</span></a> can be
handed in <code class=
"varname">PATCH_DIST_ARGS</code>. See <a href=
"#components.patches" title=
"7.3. patches/*">Section 7.3,
“patches/*”</a> for more details.</p>
<p>By default <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?patch+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">patch</span>(1)</span></a> is given
special args to make it fail if the patches apply
with some lines of fuzz. Please fix (regen) the
patches so that they apply cleanly. The rationale
behind this is that patches that don't apply
cleanly may end up being applied in the wrong
place, and cause severe harm there.</p>
</dd>
<dt><span class="term">configure</span></dt>
<dd>
<p>Most pieces of software need information on the
header files, system calls, and library routines
which are available in NetBSD. This is the process
known as configuration, and is usually automated.
In most cases, a script is supplied with the
source, and its invocation results in generation of
header files, Makefiles, etc.</p>
<p>If the program's distfile contains its own
configure script, this can be invoked by setting
<code class="varname">HAS_CONFIGURE</code>. If the
configure script is a GNU autoconf script,
<code class="varname">GNU_CONFIGURE</code> should
be specified instead. In either case, any arguments
to the configure script can be specified in the
<code class="varname">CONFIGURE_ARGS</code>
variable, and the configure script's name can be
set in <code class=
"varname">CONFIGURE_SCRIPT</code> if it differs
from the default “<span class=
"quote">configure</span>”. Here's an example
from the <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/sysutils/top/README.html"
class="pkgname">sysutils/top</a> package:</p>
<pre class="programlisting">
HAS_CONFIGURE= yes
CONFIGURE_SCRIPT= Configure
CONFIGURE_ARGS+= netbsd13
</pre>
<p>If the program uses an Imakefile for
configuration, the appropriate steps can be invoked
by setting <code class="varname">USE_IMAKE</code>
to “<span class="quote">YES</span>”.
(If you only want the package installed in
<code class="varname">$X11PREFIX</code> but xmkmf
not being run, set <code class=
"varname">USE_X11BASE</code> instead!)</p>
</dd>
<dt><span class="term">build</span></dt>
<dd>
<p>Once configuration has taken place, the software
will be built by invoking <code class=
"varname">$MAKE_PROGRAM</code> on <code class=
"varname">$MAKEFILE</code> with <code class=
"varname">$BUILD_TARGET</code> as the target to
build. The default <code class=
"varname">MAKE_PROGRAM</code> is
“<span class="quote">gmake</span>” if
<code class="varname">USE_TOOLS</code> contains
“<span class="quote">gmake</span>”,
“<span class="quote">make</span>”
otherwise. <code class="varname">MAKEFILE</code> is
set to “<span class=
"quote">Makefile</span>” by default, and
<code class="varname">BUILD_TARGET</code> defaults
to “<span class="quote">all</span>”.
Any of these variables can be set in the package's
Makefile to change the default build process.</p>
</dd>
<dt><span class="term">install</span></dt>
<dd>
<p>Once the build stage has completed, the final
step is to install the software in public
directories, so users can access the programs and
files. As in the build-target, <code class=
"varname">$MAKE_PROGRAM</code> is invoked on
<code class="varname">$MAKEFILE</code> here, but
with the <code class=
"varname">$INSTALL_TARGET</code> instead, the
latter defaulting to “<span class=
"quote">install</span>” (plus
“<span class=
"quote">install.man</span>”, if <code class=
"varname">USE_IMAKE</code> is set).</p>
</dd>
</dl>
</div>
<p>If no target is specified, the default is
“<span class="quote">build</span>”. If a
subsequent stage is requested, all prior stages are made:
e.g. <span><strong class="command">make
build</strong></span> will also perform the equivalent
of:</p>
<pre class="programlisting">
make fetch
make checksum
make extract
make patch
make configure
make build
</pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"build.helpful-targets" id=
"build.helpful-targets"></a>12.3. Other
helpful targets</h2>
</div>
</div>
</div>
<div class="variablelist">
<dl>
<dt><span class="term">pre/post-*</span></dt>
<dd>
<p>For any of the main targets described in the
previous section, two auxiliary targets exist with
“<span class="quote">pre-</span>” and
“<span class="quote">post-</span>” used
as a prefix for the main target's name. These
targets are invoked before and after the main
target is called, allowing extra configuration or
installation steps be performed from a package's
Makefile, for example, which a program's configure
script or install target omitted.</p>
</dd>
<dt><span class="term">do-*</span></dt>
<dd>
<p>Should one of the main targets do the wrong
thing, and should there be no variable to fix this,
you can redefine it with the do-* target. (Note
that redefining the target itself instead of the
do-* target is a bad idea, as the pre-* and post-*
targets won't be called anymore, etc.) You will not
usually need to do this.</p>
</dd>
<dt><span class="term">reinstall</span></dt>
<dd>
<p>If you did a <span><strong class="command">make
install</strong></span> and you noticed some file
was not installed properly, you can repeat the
installation with this target, which will ignore
the “<span class="quote">already
installed</span>” flag.</p>
</dd>
<dt><span class="term">deinstall</span></dt>
<dd>
<p>This target does a <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_delete</span>(1)</span></a> in
the current directory, effectively de-installing
the package. The following variables can be used to
tune the behaviour:</p>
<div class="variablelist">
<dl>
<dt><span class="term"><code class=
"varname">PKG_VERBOSE</code></span></dt>
<dd>
<p>Add a "-v" to the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_delete</span>(1)</span></a>
command.</p>
</dd>
<dt><span class="term"><code class=
"varname">DEINSTALLDEPENDS</code></span></dt>
<dd>
<p>Remove all packages that require (depend
on) the given package. This can be used to
remove any packages that may have been pulled
in by a given package, e.g. if
<span><strong class="command">make deinstall
DEINSTALLDEPENDS=1</strong></span> is done in
<code class="filename">pkgsrc/x11/kde</code>,
this is likely to remove whole KDE. Works by
adding “<span class=
"quote">-R</span>” to the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_delete</span>(1)</span></a>
command line.</p>
</dd>
</dl>
</div>
</dd>
<dt><span class="term">update</span></dt>
<dd>
<p>This target causes the current package to be
updated to the latest version. The package and all
depending packages first get de-installed, then
current versions of the corresponding packages get
compiled and installed. This is similar to manually
noting which packages are currently installed, then
performing a series of <span><strong class=
"command">make deinstall</strong></span> and
<span><strong class="command">make
install</strong></span> (or whatever <code class=
"varname">UPDATE_TARGET</code> is set to) for these
packages.</p>
<p>You can use the “<span class=
"quote">update</span>” target to resume
package updating in case a previous
<span><strong class="command">make
update</strong></span> was interrupted for some
reason. However, in this case, make sure you don't
call <span><strong class="command">make
clean</strong></span> or otherwise remove the list
of dependent packages in <code class=
"varname">WRKDIR</code>. Otherwise you lose the
ability to automatically update the current package
along with the dependent packages you have
installed.</p>
<p>Resuming an interrupted <span><strong class=
"command">make update</strong></span> will only
work as long as the package tree remains unchanged.
If the source code for one of the packages to be
updated has been changed, resuming
<span><strong class="command">make
update</strong></span> will most certainly
fail!</p>
<p>The following variables can be used either on
the command line or in <code class=
"filename">/etc/mk.conf</code> to alter the
behaviour of <span><strong class="command">make
update</strong></span>:</p>
<div class="variablelist">
<dl>
<dt><span class="term"><code class=
"varname">UPDATE_TARGET</code></span></dt>
<dd>
<p>Install target to recursively use for the
updated package and the dependent packages.
Defaults to <code class=
"varname">DEPENDS_TARGET</code> if set,
“<span class=
"quote">install</span>” otherwise for
<span><strong class="command">make
update</strong></span>. e.g.
<span><strong class="command">make update
UPDATE_TARGET=package</strong></span></p>
</dd>
<dt><span class="term"><code class=
"varname">NOCLEAN</code></span></dt>
<dd>
<p>Don't clean up after updating. Useful if
you want to leave the work sources of the
updated packages around for inspection or
other purposes. Be sure you eventually clean
up the source tree (see the
“<span class=
"quote">clean-update</span>” target
below) or you may run into troubles with old
source code still lying around on your next
<span><strong class=
"command">make</strong></span> or
<span><strong class="command">make
update</strong></span>.</p>
</dd>
<dt><span class="term"><code class=
"varname">REINSTALL</code></span></dt>
<dd>
<p>Deinstall each package before installing
(making <code class=
"varname">DEPENDS_TARGET</code>). This may be
necessary if the “<span class=
"quote">clean-update</span>” target
(see below) was called after interrupting a
running <span><strong class="command">make
update</strong></span>.</p>
</dd>
<dt><span class="term"><code class=
"varname">DEPENDS_TARGET</code></span></dt>
<dd>
<p>Allows you to disable recursion and
hardcode the target for packages. The default
is “<span class=
"quote">update</span>” for the update
target, facilitating a recursive update of
prerequisite packages. Only set <code class=
"varname">DEPENDS_TARGET</code> if you want
to disable recursive updates. Use
<code class="varname">UPDATE_TARGET</code>
instead to just set a specific target for
each package to be installed during
<span><strong class="command">make
update</strong></span> (see above).</p>
</dd>
</dl>
</div>
</dd>
<dt><span class="term">clean-update</span></dt>
<dd>
<p>Clean the source tree for all packages that
would get updated if <span><strong class=
"command">make update</strong></span> was called
from the current directory. This target should not
be used if the current package (or any of its
depending packages) have already been de-installed
(e.g., after calling <span><strong class=
"command">make update</strong></span>) or you may
lose some packages you intended to update. As a
rule of thumb: only use this target <span class=
"emphasis"><em>before</em></span> the first time
you run <span><strong class="command">make
update</strong></span> and only if you have a dirty
package tree (e.g., if you used <code class=
"varname">NOCLEAN</code>).</p>
<p>If you unsure about whether your tree is clean
you can either perform a <span><strong class=
"command">make clean</strong></span> at the top of
the tree, or use the following sequence of commands
from the directory of the package you want to
update (<span class=
"emphasis"><em>before</em></span> running
<span><strong class="command">make
update</strong></span> for the first time,
otherwise you lose all the packages you wanted to
update!):</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make clean-update</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>make clean CLEANDEPENDS=YES</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>make update</code></strong>
</pre>
<p>The following variables can be used either on
the command line or in <code class=
"filename">/etc/mk.conf</code> to alter the
behaviour of <span><strong class="command">make
clean-update</strong></span>:</p>
<div class="variablelist">
<dl>
<dt><span class="term"><code class=
"varname">CLEAR_DIRLIST</code></span></dt>
<dd>
<p>After <span><strong class="command">make
clean</strong></span>, do not reconstruct the
list of directories to update for this
package. Only use this if
<span><strong class="command">make
update</strong></span> successfully installed
all packages you wanted to update. Normally,
this is done automatically on
<span><strong class="command">make
update</strong></span>, but may have been
suppressed by the <code class=
"varname">NOCLEAN</code> variable (see
above).</p>
</dd>
</dl>
</div>
</dd>
<dt><span class="term">info</span></dt>
<dd>
<p>This target invokes <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_info+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_info</span>(1)</span></a> for
the current package. You can use this to check
which version of a package is installed.</p>
</dd>
<dt><span class="term">readme</span></dt>
<dd>
<p>This target generates a <code class=
"filename">README.html</code> file, which can be
viewed using a browser such as <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/mozilla/README.html"
class="pkgname">www/mozilla</a> or <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/links/README.html"
class="pkgname">www/links</a>. The generated files
contain references to any packages which are in the
<code class="varname">PACKAGES</code> directory on
the local host. The generated files can be made to
refer to URLs based on <code class=
"varname">FTP_PKG_URL_HOST</code> and <code class=
"varname">FTP_PKG_URL_DIR</code>. For example, if I
wanted to generate <code class=
"filename">README.html</code> files which pointed
to binary packages on the local machine, in the
directory <code class=
"filename">/usr/packages</code>, set <code class=
"varname">FTP_PKG_URL_HOST=file://localhost</code>
and <code class=
"varname">FTP_PKG_URL_DIR=/usr/packages</code>. The
<code class="varname">${PACKAGES}</code> directory
and its subdirectories will be searched for all the
binary packages.</p>
</dd>
<dt><span class="term">readme-all</span></dt>
<dd>
<p>Use this target to create a file <code class=
"filename">README-all.html</code> which contains a
list of all packages currently available in the
NetBSD Packages Collection, together with the
category they belong to and a short description.
This file is compiled from the <code class=
"filename">pkgsrc/*/README.html</code> files, so be
sure to run this <span class=
"emphasis"><em>after</em></span> a
<span><strong class="command">make
readme</strong></span>.</p>
</dd>
<dt><span class="term">cdrom-readme</span></dt>
<dd>
<p>This is very much the same as the
“<span class="quote">readme</span>”
target (see above), but is to be used when
generating a pkgsrc tree to be written to a CD-ROM.
This target also produces <code class=
"filename">README.html</code> files, and can be
made to refer to URLs based on <code class=
"varname">CDROM_PKG_URL_HOST</code> and
<code class="varname">CDROM_PKG_URL_DIR</code>.</p>
</dd>
<dt><span class="term">show-distfiles</span></dt>
<dd>
<p>This target shows which distfiles and patchfiles
are needed to build the package. (<code class=
"varname">DISTFILES</code> and <code class=
"varname">PATCHFILES</code>, but not <code class=
"filename">patches/*</code>)</p>
</dd>
<dt><span class="term">show-downlevel</span></dt>
<dd>
<p>This target shows nothing if the package is not
installed. If a version of this package is
installed, but is not the version provided in this
version of pkgsrc, then a warning message is
displayed. This target can be used to show which of
your installed packages are downlevel, and so the
old versions can be deleted, and the current ones
added.</p>
</dd>
<dt><span class="term">show-pkgsrc-dir</span></dt>
<dd>
<p>This target shows the directory in the pkgsrc
hierarchy from which the package can be built and
installed. This may not be the same directory as
the one from which the package was installed. This
target is intended to be used by people who may
wish to upgrade many packages on a single host, and
can be invoked from the top-level pkgsrc Makefile
by using the “<span class=
"quote">show-host-specific-pkgs</span>”
target.</p>
</dd>
<dt><span class=
"term">show-installed-depends</span></dt>
<dd>
<p>This target shows which installed packages match
the current package's <code class=
"varname">DEPENDS</code>. Useful if out of date
dependencies are causing build problems.</p>
</dd>
<dt><span class="term">check-shlibs</span></dt>
<dd>
<p>After a package is installed, check all its
binaries and (on ELF platforms) shared libraries to
see if they find the shared libs they need. Run by
default if <code class=
"varname">PKG_DEVELOPER</code> is set in
<code class="filename">/etc/mk.conf</code>.</p>
</dd>
<dt><span class="term">print-PLIST</span></dt>
<dd>
<p>After a “<span class="quote">make
install</span>” from a new or upgraded pkg,
this prints out an attempt to generate a new
<code class="filename">PLIST</code> from a
<span><strong class="command">find -newer
work/.extract_done</strong></span>. An attempt is
made to care for shared libs etc., but it is
<span class="emphasis"><em>strongly</em></span>
recommended to review the result before putting it
into <code class="filename">PLIST</code>. On
upgrades, it's useful to diff the output of this
command against an already existing <code class=
"filename">PLIST</code> file.</p>
<p>If the package installs files via <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?tar+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">tar</span>(1)</span></a> or other
methods that don't update file access times, be
sure to add these files manually to your
<code class="filename">PLIST</code>, as the
“<span class="quote">find
-newer</span>” command used by this target
won't catch them!</p>
<p>See <a href="#print-PLIST" title=
"9.3. Tweaking output of make print-PLIST">Section 9.3,
“Tweaking output of <span><strong class=
"command">make
print-PLIST</strong></span>”</a> for more
information on this target.</p>
</dd>
<dt><span class="term">bulk-package</span></dt>
<dd>
<p>Used to do bulk builds. If an appropriate binary
package already exists, no action is taken. If not,
this target will compile, install and package it
(and it's depends, if <code class=
"varname">PKG_DEPENDS</code> is set properly. See
<a href="#binary.configuration" title=
"5.3.1. Configuration">Section 5.3.1,
“Configuration”</a>. After creating the
binary package, the sources, the just-installed
package and it's required packages are removed,
preserving free disk space.</p>
<p><span class="emphasis"><em>Beware that this
target may deinstall all packages installed on a
system!</em></span></p>
</dd>
<dt><span class="term">bulk-install</span></dt>
<dd>
<p>Used during bulk-installs to install required
packages. If an upto-date binary package is
available, it will be installed via <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_add</span>(1)</span></a>. If
not, <span><strong class="command">make
bulk-package</strong></span> will be executed, but
the installed binary not be removed.</p>
<p>A binary package is considered
“<span class="quote">upto-date</span>”
to be installed via <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_add</span>(1)</span></a>
if:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>None of the package's files (<code class=
"filename">Makefile</code>, ...) were
modified since it was built.</p>
</li>
<li>
<p>None of the package's required (binary)
packages were modified since it was
built.</p>
</li>
</ul>
</div>
<p><span class="emphasis"><em>Beware that this
target may deinstall all packages installed on a
system!</em></span></p>
</dd>
</dl>
</div>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="fixes" id=
"fixes"></a>Chapter 13. Notes on fixes for
packages</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href=
"#general-operation">13.1. General
operation</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#pulling-vars-from-etc-mk.conf">13.1.1. How to
pull in variables from /etc/mk.conf</a></span></dt>
<dt><span class="sect2"><a href=
"#where-to-install-documentation">13.1.2. Where to
install documentation</a></span></dt>
<dt><span class="sect2"><a href=
"#restricted-packages">13.1.3. Restricted
packages</a></span></dt>
<dt><span class="sect2"><a href=
"#dependencies">13.1.4. Handling
dependencies</a></span></dt>
<dt><span class="sect2"><a href=
"#conflicts">13.1.5. Handling conflicts with other
packages</a></span></dt>
<dt><span class="sect2"><a href=
"#not-building-packages">13.1.6. Packages that
cannot or should not be built</a></span></dt>
<dt><span class="sect2"><a href=
"#undeletable-packages">13.1.7. Packages which
should not be deleted, once
installed</a></span></dt>
<dt><span class="sect2"><a href=
"#security-handling">13.1.8. Handling packages with
security problems</a></span></dt>
<dt><span class="sect2"><a href=
"#compiler-bugs">13.1.9. How to handle compiler
bugs</a></span></dt>
<dt><span class="sect2"><a href=
"#bumping-pkgrevision">13.1.10. How to handle
incrementing versions when fixing an existing
package</a></span></dt>
<dt><span class="sect2"><a href=
"#portability-of-packages">13.1.11. Portability of
packages</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#downloading-issues">13.2. Possible downloading
issues</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#no-plain-download">13.2.1. Packages whose
distfiles aren't available for plain
downloading</a></span></dt>
<dt><span class="sect2"><a href=
"#modified-distfiles-same-name">13.2.2. How to
handle modified distfiles with the 'old'
name</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#configuration-gotchas">13.3. Configuration
gotchas</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#fixes.libtool">13.3.1. Shared libraries -
libtool</a></span></dt>
<dt><span class="sect2"><a href=
"#using-libtool">13.3.2. Using libtool on GNU
packages that already support
libtool</a></span></dt>
<dt><span class="sect2"><a href=
"#autoconf-automake">13.3.3. GNU
Autoconf/Automake</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#building-considerations">13.4. Building
considerations</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#cpp-defines">13.4.1. CPP defines</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#package-specific-actions">13.5. Package specific
actions</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#package-configuration-files">13.5.1. Package
configuration files</a></span></dt>
<dt><span class="sect2"><a href=
"#user-interaction">13.5.2. User
interaction</a></span></dt>
<dt><span class="sect2"><a href=
"#handling-licenses">13.5.3. Handling
licenses</a></span></dt>
<dt><span class="sect2"><a href=
"#creating-accounts">13.5.4. Creating an account
from a package</a></span></dt>
<dt><span class="sect2"><a href=
"#installing-score-files">13.5.5. Installing score
files</a></span></dt>
<dt><span class="sect2"><a href=
"#login-shells">13.5.6. Packages providing login
shells</a></span></dt>
<dt><span class="sect2"><a href=
"#perl-scripts">13.5.7. Packages containing perl
scripts</a></span></dt>
<dt><span class="sect2"><a href=
"#hardcoded-paths">13.5.8. Packages with hardcoded
paths to other interpreters</a></span></dt>
<dt><span class="sect2"><a href=
"#perl-modules">13.5.9. Packages installing perl
modules</a></span></dt>
<dt><span class="sect2"><a href=
"#faq.info-files">13.5.10. Packages installing info
files</a></span></dt>
<dt><span class="sect2"><a href=
"#gconf2-data-files">13.5.11. Packages installing
GConf2 data files</a></span></dt>
<dt><span class="sect2"><a href=
"#scrollkeeper-data-files">13.5.12. Packages
installing scrollkeeper data files</a></span></dt>
<dt><span class="sect2"><a href=
"#x11-fonts">13.5.13. Packages installing X11
fonts</a></span></dt>
<dt><span class="sect2"><a href=
"#gtk2-modules">13.5.14. Packages installing GTK2
modules</a></span></dt>
<dt><span class="sect2"><a href=
"#sgml-xml-data">13.5.15. Packages installing SGML
or XML data</a></span></dt>
<dt><span class="sect2"><a href=
"#mime-database">13.5.16. Packages installing
extensions to the MIME database</a></span></dt>
<dt><span class="sect2"><a href=
"#intltool">13.5.17. Packages using
intltool</a></span></dt>
<dt><span class="sect2"><a href=
"#startup-scripts">13.5.18. Packages installing
startup scripts</a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href=
"#feedback-to-author">13.6. Feedback to the
author</a></span></dt>
</dl>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"general-operation" id=
"general-operation"></a>13.1. General
operation</h2>
</div>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"pulling-vars-from-etc-mk.conf" id=
"pulling-vars-from-etc-mk.conf"></a>13.1.1. How
to pull in variables from /etc/mk.conf</h3>
</div>
</div>
</div>
<p>The problem with package-defined variables that can
be overridden via <code class="varname">MAKECONF</code>
or <code class="filename">/etc/mk.conf</code> is that
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">make</span>(1)</span></a> expands a
variable as it is used, but evaluates preprocessor like
statements (.if, .ifdef and .ifndef) as they are read.
So, to use any variable (which may be set in
<code class="filename">/etc/mk.conf</code>) in one of
the .if* statements, the file <code class=
"filename">/etc/mk.conf</code> must be included before
that .if* statement.</p>
<p>Rather than have a number of ad-hoc ways of
including <code class="filename">/etc/mk.conf</code>,
should it exist, or <code class=
"varname">MAKECONF</code>, should it exist, include the
<code class="filename">pkgsrc/mk/bsd.prefs.mk</code>
file in the package Makefile before any
preprocessor-like .if, .ifdef, or .ifndef
statements:</p>
<pre class="programlisting">
.include "../../mk/bsd.prefs.mk"
.if defined(USE_MENUS)
...
.endif
</pre>
<p>If you wish to set the <code class=
"varname">CFLAGS</code> variable in <code class=
"filename">/etc/mk.conf</code> please make sure to
use:</p>
<pre class="programlisting">
CFLAGS+= -your -flags
</pre>
<p>Using <code class="varname">CFLAGS=</code> (i.e.
without the “<span class="quote">+</span>”)
may lead to problems with packages that need to add
their own flags. Also, you may want to take a look at
the <a xmlns="http://www.w3.org/TR/xhtml1/transitional"
href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/cpuflags/README.html"
class="pkgname">devel/cpuflags</a> package if you're
interested in optimization for the current CPU.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"where-to-install-documentation" id=
"where-to-install-documentation"></a>13.1.2. Where
to install documentation</h3>
</div>
</div>
</div>
<p>Documentation should be installed into <code class=
"filename">${PREFIX}/share/doc/${PKGBASE}</code> or
<code class=
"filename">${PREFIX}/share/doc/${PKGNAME}</code> (the
latter includes the version number of the package).</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="restricted-packages"
id=
"restricted-packages"></a>13.1.3. Restricted
packages</h3>
</div>
</div>
</div>
<p>Some licenses restrict how software may be
re-distributed. In order to satisfy these restrictions,
the package system defines five make variables that can
be set to note these restrictions:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><code class="varname">RESTRICTED</code></p>
<p>This variable should be set whenever a
restriction exists (regardless of its kind). Set
this variable to a string containing the reason
for the restriction.</p>
</li>
<li>
<p><code class=
"varname">NO_BIN_ON_CDROM</code></p>
<p>Binaries may not be placed on CD-ROM. Set this
variable to <code class=
"varname">${RESTRICTED}</code> whenever a binary
package may not be included on a CD-ROM.</p>
</li>
<li>
<p><code class="varname">NO_BIN_ON_FTP</code></p>
<p>Binaries may not be placed on an FTP server.
Set this variable to <code class=
"varname">${RESTRICTED}</code> whenever a binary
package may not not be made available on the
Internet.</p>
</li>
<li>
<p><code class=
"varname">NO_SRC_ON_CDROM</code></p>
<p>Distfiles may not be placed on CD-ROM. Set
this variable to <code class=
"varname">${RESTRICTED}</code> if re-distribution
of the source code or other distfile(s) is not
allowed on CD-ROMs.</p>
</li>
<li>
<p><code class="varname">NO_SRC_ON_FTP</code></p>
<p>Distfiles may not be placed on FTP. Set this
variable to <code class=
"varname">${RESTRICTED}</code> if re-distribution
of the source code or other distfile(s) via the
Internet is not allowed.</p>
</li>
</ul>
</div>
<p>Please note that the use of <code class=
"varname">NO_PACKAGE</code>, <code class=
"varname">IGNORE</code>, <code class=
"varname">NO_CDROM</code>, or other generic make
variables to denote restrictions is deprecated, because
they unconditionally prevent users from generating
binary packages!</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="dependencies" id=
"dependencies"></a>13.1.4. Handling
dependencies</h3>
</div>
</div>
</div>
<p>Your package may depend on some other package being
present - and there are various ways of expressing this
dependency. pkgsrc supports the <code class=
"varname">BUILD_DEPENDS</code> and <code class=
"varname">DEPENDS</code> definitions, as well as
dependencies via <code class=
"filename">buildlink3.mk</code>, which is the preferred
way to handle dependencies, and which uses the
variables named above. See <a href="#buildlink" title=
"Chapter 10. Buildlink methodology">Chapter 10,
<i>Buildlink methodology</i></a> for more
information.</p>
<p>The basic difference between the two variables is as
follows: The <code class="varname">DEPENDS</code>
definition registers that pre-requisite in the binary
package so it will be pulled in when the binary package
is later installed, whilst the <code class=
"varname">BUILD_DEPENDS</code> definition does not,
marking a dependency that is only needed for building
the package.</p>
<p>This means that if you only need a package present
whilst you are building, it should be noted as a
<code class="varname">BUILD_DEPENDS</code>.</p>
<p>The format for a <code class=
"varname">BUILD_DEPENDS</code> and a <code class=
"varname">DEPENDS</code> definition is:</p>
<pre class="programlisting">
<pre-req-package-name>:../../<category>/<pre-req-package>
</pre>
<p>Please note that the “<span class=
"quote">pre-req-package-name</span>” may include
any of the wildcard version numbers recognized by
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_info+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_info</span>(1)</span></a>.</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>If your package needs another package's
binaries or libraries to build or run, and if
that package has a <code class=
"filename">buildlink3.mk</code> file available,
use it:</p>
<pre class="programlisting">
.include "../../graphics/jpeg/buildlink3.mk"
</pre>
</li>
<li>
<p>If your package needs to use another package
to build itself and there is no <code class=
"filename">buildlink3.mk</code> file available,
use the <code class=
"varname">BUILD_DEPENDS</code> definition:</p>
<pre class="programlisting">
BUILD_DEPENDS+= autoconf-2.13:../../devel/autoconf
</pre>
</li>
<li>
<p>If your package needs a library with which to
link and again there is no <code class=
"filename">buildlink3.mk</code> file available,
this is specified using the <code class=
"varname">DEPENDS</code> definition. An example
of this is the <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/print/lyx/README.html"
class="pkgname">print/lyx</a> package, which uses
the xpm library, version 3.4j to build:</p>
<pre class="programlisting">
DEPENDS+= xpm-3.4j:../../graphics/xpm
</pre>
<p>You can also use wildcards in package
dependences:</p>
<pre class="programlisting">
DEPENDS+= xpm-[0-9]*:../../graphics/xpm
</pre>
<p>Note that such wildcard dependencies are
retained when creating binary packages. The
dependency is checked when installing the binary
package and any package which matches the pattern
will be used. Wildcard dependencies should be
used with care.</p>
<p>The “<span class=
"quote">-[0-9]*</span>” should be used
instead of “<span class=
"quote">-*</span>” to avoid potentially
ambiguous matches such as “<span class=
"quote">tk-postgresql</span>” matching a
“<span class="quote">tk-*</span>”
<code class="varname">DEPENDS</code>.</p>
<p>Wildcards can also be used to specify that a
package will only build against a certain minimum
version of a pre-requisite:</p>
<pre class="programlisting">
DEPENDS+= tiff>=3.5.4:../../graphics/tiff
</pre>
<p>This means that the package will build against
version 3.5.4 of the tiff library or newer. Such
a dependency may be warranted if, for example,
the API of the library has changed with version
3.5.4 and a package would not compile against an
earlier version of tiff.</p>
<p>Please note that such dependencies should only
be updated if a package requires a newer
pre-requisite, but not to denote recommendations
such as security updates or ABI changes that do
not prevent a package from building correctly.
Such recommendations can be expressed using
<code class="varname">RECOMMENDED</code>:</p>
<pre class="programlisting">
RECOMMENDED+= tiff>=3.6.1:../../graphics/tiff
</pre>
<p>In addition to the above <code class=
"varname">DEPENDS</code> line, this denotes that
while a package will build against
tiff>=3.5.4, at least version 3.6.1 is
recommended. <code class=
"varname">RECOMMENDED</code> entries will be
turned into dependencies unless explicitly
ignored (in which case a warning will be
printed). Packages that are built with
recommendations ignored may not be uploaded to
ftp.NetBSD.org by developers and should not be
used across different systems that may have
different versions of binary packages
installed.</p>
<p>For security fixes, please update the package
vulnerabilities file as well as setting
<code class="varname">RECOMMENDED</code>, see
<a href="#security-handling" title=
"13.1.8. Handling packages with security problems">
Section 13.1.8, “Handling packages with
security problems”</a> for more
information.</p>
</li>
<li>
<p>If your package needs some executable to be
able to run correctly and if there's no
<code class="filename">buildlink3.mk</code> file,
this is specified using the <code class=
"varname">DEPENDS</code> variable. The <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/print/lyx/README.html"
class="pkgname">print/lyx</a> package needs to be
able to execute the latex binary from the teTeX
package when it runs, and that is specified:</p>
<pre class="programlisting">
DEPENDS+= teTeX-[0-9]*:../../print/teTeX
</pre>
<p>The comment about wildcard dependencies from
previous paragraph applies here, too.</p>
</li>
</ol>
</div>
<p>If your package needs files from another package to
build, see the first part of the “<span class=
"quote">do-configure</span>” target <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/print/ghostscript5/README.html"
class="pkgname">print/ghostscript5</a> package (it
relies on the jpeg sources being present in source form
during the build):</p>
<pre class="programlisting">
if [ ! -e ${_PKGSRCDIR}/graphics/jpeg/${WRKDIR:T}/jpeg-6b ]; then \
cd ${_PKGSRCDIR}/../../graphics/jpeg && ${MAKE} extract; \
fi
</pre>
<p>If you build any other packages that way, please
make sure the working files are deleted too when this
package's working files are cleaned up. The easiest way
to do so is by adding a pre-clean target:</p>
<pre class="programlisting">
pre-clean:
cd ${_PKGSRCDIR}/../../graphics/jpeg && ${MAKE} clean
</pre>
<p>Please also note the <code class=
"varname">BUILD_USES_MSGFMT</code> and <code class=
"varname">BUILD_USES_GETTEXT_M4</code> definitions,
which are provided as convenience definitions. The
former works out whether <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?msgfmt+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">msgfmt</span>(1)</span></a> is part of
the base system, and, if it isn't, installs the
<a xmlns="http://www.w3.org/TR/xhtml1/transitional"
href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/gettext/README.html"
class="pkgname">devel/gettext</a> package. The latter
adds a build dependency on either an installed version
of an older gettext package, or if it isn't, installs
the <a xmlns="http://www.w3.org/TR/xhtml1/transitional"
href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/gettext-m4/README.html"
class="pkgname">devel/gettext-m4</a> package.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="conflicts" id=
"conflicts"></a>13.1.5. Handling conflicts
with other packages</h3>
</div>
</div>
</div>
<p>Your package may conflict with other packages a user
might already have installed on his system, e.g. if
your package installs the same set of files like
another package in our pkgsrc tree.</p>
<p>In this case you can set <code class=
"varname">CONFLICTS</code> to a space separated list of
packages (including version string) your package
conflicts with.</p>
<p>For example <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/Xaw3d/README.html"
class="pkgname">x11/Xaw3d</a> and <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/Xaw-Xpm/README.html"
class="pkgname">x11/Xaw-Xpm</a> install provide the
same shared library, thus you set in <code class=
"filename">pkgsrc/x11/Xaw3d/Makefile</code>:</p>
<pre class="programlisting">
CONFLICTS= Xaw-Xpm-[0-9]*
</pre>
<p>and in <code class=
"filename">pkgsrc/x11/Xaw-Xpm/Makefile</code>:</p>
<pre class="programlisting">
CONFLICTS= Xaw3d-[0-9]*
</pre>
<p>Packages will automatically conflict with other
packages with the name prefix and a different version
string. “<span class=
"quote">Xaw3d-1.5</span>” e.g. will automatically
conflict with the older version “<span class=
"quote">Xaw3d-1.3</span>”.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="not-building-packages"
id=
"not-building-packages"></a>13.1.6. Packages
that cannot or should not be built</h3>
</div>
</div>
</div>
<p>There are several reasons why a package might be
instructed to not build under certain circumstances. If
the package builds and runs on most platforms, the
exceptions should be noted with <code class=
"varname">NOT_FOR_PLATFORM</code>. If the package
builds and runs on a small handful of platforms, set
<code class="varname">ONLY_FOR_PLATFORM</code> instead.
If the package should be skipped (for example, because
it provides functionality already provided by the
system), set <code class=
"varname">PKG_SKIP_REASON</code> to a descriptive
message. If the package should fail because some
preconditions are not met, set <code class=
"varname">PKG_FAIL_REASON</code> to a descriptive
message.</p>
<p><code class="varname">IGNORE</code> is deprecated
because it didn't provide enough information to
determine whether the build should fail.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="undeletable-packages"
id=
"undeletable-packages"></a>13.1.7. Packages
which should not be deleted, once installed</h3>
</div>
</div>
</div>
<p>To ensure that a package may not be deleted, once it
has been installed, the <code class=
"varname">PKG_PRESERVE</code> definition should be set
in the package Makefile. This will be carried into any
binary package that is made from this pkgsrc entry. A
“<span class="quote">preserved</span>”
package will not be deleted using <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">pkg_delete</span>(1)</span></a> unless
the “<span class="quote">-f</span>” option
is used.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="security-handling" id=
"security-handling"></a>13.1.8. Handling
packages with security problems</h3>
</div>
</div>
</div>
<p>When a vulnerability is found, this should be noted
in <code class=
"filename">localsrc/security/advisories/pkg-vulnerabilities</code>,
and after the commit of that file, it should be copied
to both <code class=
"filename">/pub/NetBSD/packages/distfiles/pkg-vulnerabilities</code>
and <code class=
"filename">/pub/NetBSD/packages/distfiles/vulnerabilities</code>
on ftp.NetBSD.org using <code class=
"filename">localsrc/security/advisories/Makefile</code>.
In addition, if a <code class=
"filename">buildlink3.mk</code> file exists for an
affected package, bumping <code class=
"varname">PKGREVISION</code> and creating a
corresponding <code class=
"varname">BUILDLINK_RECOMMENDED.<em class=
"replaceable"><code>pkg</code></em></code> entry should
be considered. See <a href="#buildlink" title=
"Chapter 10. Buildlink methodology">Chapter 10,
<i>Buildlink methodology</i></a> for more information
about writing <code class=
"filename">buildlink3.mk</code> files and <code class=
"varname">BUILDLINK_*</code> definitions.</p>
<p>Also, if the fix should be applied to the stable
pkgsrc branch, be sure to submit a pullup request!</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="compiler-bugs" id=
"compiler-bugs"></a>13.1.9. How to handle
compiler bugs</h3>
</div>
</div>
</div>
<p>Some source files trigger bugs in the compiler,
based on combinations of compiler version and
architecture and almost always relation to optimisation
being enabled. Common symptoms are gcc internal errors
or never finishing compiling a file.</p>
<p>Typically a workaround involves testing the
<code class="varname">MACHINE_ARCH</code> and compiler
version, disabling optimisation for that
file/<code class="varname">MACHINE_ARCH</code>/compiler
combination, and documenting it in <code class=
"filename">pkgsrc/doc/HACKS</code>. See that file for a
number of examples!</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="bumping-pkgrevision"
id="bumping-pkgrevision"></a>13.1.10. How to
handle incrementing versions when fixing an
existing package</h3>
</div>
</div>
</div>
<p>When making fixes to an existing package it can be
useful to change the version number in <code class=
"varname">PKGNAME</code>. To avoid conflicting with
future versions by the original author, a
“<span class="quote">nb1</span>”,
“<span class="quote">nb2</span>”, ...
suffix can be used on package versions by setting
<code class="varname">PKGREVISION=1</code> (2, ...).
The “<span class="quote">nb</span>” is
treated like a “<span class=
"quote">.</span>” by the pkg tools. e.g.</p>
<pre class="programlisting">
DISTNAME= foo-17.42
PKGREVISION= 9
</pre>
<p>will result in a <code class=
"varname">PKGNAME</code> of “<span class=
"quote">foo-17.42nb9</span>”.</p>
<p>When a new release of the package is released, the
<code class="varname">PKGREVISION</code> should be
removed. e.g. on a new minor release of the above
package, things should be like:</p>
<pre class="programlisting">
DISTNAME= foo-17.43
</pre>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"portability-of-packages" id=
"portability-of-packages"></a>13.1.11. Portability
of packages</h3>
</div>
</div>
</div>
<p>One appealing feature of pkgsrc is that it runs on
many different platforms. As a result, it is important
to ensure, where possible, that packages in pkgsrc are
portable. There are some particular details you should
pay attention to while working on pkgsrc.</p>
<div class="sect3" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="install-scripts" id=
"install-scripts"></a>13.1.11.1. ${INSTALL},
${INSTALL_DATA_DIR}, ...</h4>
</div>
</div>
</div>
<p>The BSD-compatible <span><strong class=
"command">install</strong></span> supplied with some
operating systems will not perform more than one
operation at a time. As such, you should call
“<span class="quote">${INSTALL}</span>”,
etc. like this:</p>
<pre class="programlisting">
${INSTALL_DATA_DIR} ${PREFIX}/dir1
${INSTALL_DATA_DIR} ${PREFIX}/dir2
</pre>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"downloading-issues" id=
"downloading-issues"></a>13.2. Possible
downloading issues</h2>
</div>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="no-plain-download" id=
"no-plain-download"></a>13.2.1. Packages
whose distfiles aren't available for plain
downloading</h3>
</div>
</div>
</div>
<p>If you need to download from a dynamic URL you can
set <code class="varname">DYNAMIC_MASTER_SITES</code>
and a <span><strong class="command">make
fetch</strong></span> will call <code class=
"filename">files/getsite.sh</code> with the name of
each file to download as an argument, expecting it to
output the URL of the directory from which to download
it. <a xmlns="http://www.w3.org/TR/xhtml1/transitional"
href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/graphics/ns-cult3d/README.html"
class="pkgname">graphics/ns-cult3d</a> is an example of
this usage.</p>
<p>If the download can't be automated, because the user
must submit personal information to apply for a
password, or must pay for the source, or whatever, you
can set <code class="varname">_FETCH_MESSAGE</code> to
a macro which displays a message explaining the
situation. <code class="varname">_FETCH_MESSAGE</code>
must be executable shell commands, not just a message.
(Generally, it executes <code class=
"varname">${ECHO}</code>). As of this writing, the
following packages use this: <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/audio/realplayer/README.html"
class="pkgname">audio/realplayer</a>, <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/cad/simian/README.html"
class="pkgname">cad/simian</a>, <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/ipv6socket/README.html"
class="pkgname">devel/ipv6socket</a>, <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/emulators/vmware-module/README.html"
class="pkgname">emulators/vmware-module</a>, <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/fonts/acroread-jpnfont/README.html"
class="pkgname">fonts/acroread-jpnfont</a>, <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/sysutils/storage-manager/README.html"
class="pkgname">sysutils/storage-manager</a>, <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/ap-aolserver/README.html"
class="pkgname">www/ap-aolserver</a>, <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/openacs/README.html"
class="pkgname">www/openacs</a>. Try to be consistent
with them.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"modified-distfiles-same-name" id=
"modified-distfiles-same-name"></a>13.2.2. How
to handle modified distfiles with the 'old'
name</h3>
</div>
</div>
</div>
<p>Sometimes authors of a software package make some
modifications after the software was released, and they
put up a new distfile without changing the package's
version number. If a package is already in pkgsrc at
that time, the checksum will no longer match. The
contents of the new distfile should be compared against
the old one before changing anything, to make sure the
distfile was really updated on purpose, and that no
trojan horse or so crept in. Then, the correct way to
work around this is to set <code class=
"varname">DIST_SUBDIR</code> to a unique directory
name, usually based on <code class=
"varname">PKGNAME_NOREV</code>. In case this happens
more often, <code class="varname">PKGNAME</code> can be
used (thus including the <code class=
"filename">nbX</code> suffix) or a date stamp can be
appended, like <code class=
"varname">${PKGNAME_NOREV}-YYYYMMDD</code>. Do not
forget regenerating the <code class=
"filename">distinfo</code> file after that, since it
contains the <code class="varname">DIST_SUBDIR</code>
path in the filenames. Furthermore, a mail to the
package's authors seems appropriate telling them that
changing distfiles after releases without changing the
file names is not good practice.</p>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"configuration-gotchas" id=
"configuration-gotchas"></a>13.3. Configuration
gotchas</h2>
</div>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="fixes.libtool" id=
"fixes.libtool"></a>13.3.1. Shared libraries
- libtool</h3>
</div>
</div>
</div>
<p>pkgsrc supports many different machines, with
different object formats like a.out and ELF, and
varying abilities to do shared library and dynamic
loading at all. To accompany this, varying commands and
options have to be passed to the compiler, linker, etc.
to get the Right Thing, which can be pretty annoying
especially if you don't have all the machines at your
hand to test things. The <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/libtool/README.html"
class="pkgname">devel/libtool</a> pkg can help here, as
it just “<span class="quote">knows</span>”
how to build both static and dynamic libraries from a
set of source files, thus being platform
independent.</p>
<p>Here's how to use libtool in a pkg in seven simple
steps:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>Add <code class=
"varname">USE_LIBTOOL=yes</code> to the package
Makefile.</p>
</li>
<li>
<p>For library objects, use “<span class=
"quote">${LIBTOOL} --mode=compile
${CC}</span>” in place of
“<span class="quote">${CC}</span>”.
You could even add it to the definition of
<code class="varname">CC</code>, if only
libraries are being built in a given Makefile.
This one command will build both PIC and non-PIC
library objects, so you need not have separate
shared and non-shared library rules.</p>
</li>
<li>
<p>For the linking of the library, remove any
“<span class="quote">ar</span>”,
“<span class="quote">ranlib</span>”,
and “<span class="quote">ld
-Bshareable</span>” commands, and instead
use:</p>
<pre class="programlisting">
${LIBTOOL} --mode=link ${CC} -o ${.TARGET:.a=.la} ${OBJS:.o=.lo} -rpath ${PREFIX}/lib -version-info major:minor
</pre>
<p>Note that the library is changed to have a
<code class="filename">.la</code> extension, and
the objects are changed to have a <code class=
"filename">.lo</code> extension. Change
<code class="varname">OBJS</code> as necessary.
This automatically creates all of the
<code class="filename">.a</code>, <code class=
"filename">.so.major.minor</code>, and ELF
symlinks (if necessary) in the build directory.
Be sure to include “<span class=
"quote">-version-info</span>”, especially
when major and minor are zero, as libtool will
otherwise strip off the shared library
version.</p>
<p>From the libtool manual:</p>
<pre class="programlisting">
So, libtool library versions are described by three integers:
CURRENT
The most recent interface number that this library implements.
REVISION
The implementation number of the CURRENT interface.
AGE
The difference between the newest and oldest interfaces that this
library implements. In other words, the library implements all the
interface numbers in the range from number `CURRENT - AGE' to
`CURRENT'.
If two libraries have identical CURRENT and AGE numbers, then the
dynamic linker chooses the library with the greater REVISION number.
</pre>
<p>The “<span class=
"quote">-release</span>” option will
produce different results for a.out and ELF
(excluding symlinks) in only one case. An ELF
library of the form “<span class=
"quote">libfoo-release.so.<span class=
"emphasis"><em>x</em></span>.<span class=
"emphasis"><em>y</em></span></span>” will
have a symlink of “<span class=
"quote">libfoo.so.<span class=
"emphasis"><em>x</em></span>.<span class=
"emphasis"><em>y</em></span></span>” on an
a.out platform. This is handled
automatically.</p>
<p>The “<span class="quote">-rpath
argument</span>” is the install directory
of the library being built.</p>
<p>In the <code class="filename">PLIST</code>,
include only the <code class=
"filename">.la</code> file, the other files will
be added automatically.</p>
</li>
<li>
<p>When linking shared object (<code class=
"filename">.so</code>) files, i.e. files that are
loaded via <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?dlopen+3+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">dlopen</span>(3)</span></a>, NOT
shared libraries, use “<span class=
"quote">-module -avoid-version</span>” to
prevent them getting version tacked on.</p>
<p>The <code class="filename">PLIST</code> file
gets the <code class="filename">foo.so</code>
entry.</p>
</li>
<li>
<p>When linking programs that depend on these
libraries <span class=
"emphasis"><em>before</em></span> they are
installed, preface the <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?cc+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">cc</span>(1)</span></a> or
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?ld+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">ld</span>(1)</span></a> line with
“<span class="quote">${LIBTOOL}
--mode=link</span>”, and it will find the
correct libraries (static or shared), but please
be aware that libtool will not allow you to
specify a relative path in -L (such as
“<span class=
"quote">-L../somelib</span>”), because it
expects you to change that argument to be the
<code class="filename">.la</code> file. e.g.</p>
<pre class="programlisting">
${LIBTOOL} --mode=link ${CC} -o someprog -L../somelib -lsomelib
</pre>
<p>should be changed to:</p>
<pre class="programlisting">
${LIBTOOL} --mode=link ${CC} -o <em class=
"replaceable"><code>someprog</code></em> <em class=
"replaceable"><code>../somelib/somelib.la</code></em>
</pre>
<p>and it will do the right thing with the
libraries.</p>
</li>
<li>
<p>When installing libraries, preface the
<a href="http://netbsd.gw.com/cgi-bin/man-cgi?install+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">install</span>(1)</span></a> or
<a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?cp+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">cp</span>(1)</span></a> command
with “<span class="quote">${LIBTOOL}
--mode=install</span>”, and change the
library name to <code class=
"filename">.la</code>. e.g.</p>
<pre class="programlisting">
${LIBTOOL} --mode=install ${BSD_INSTALL_DATA} ${SOMELIB:.a=.la} ${PREFIX}/lib
</pre>
<p>This will install the static <code class=
"filename">.a</code>, shared library, any needed
symlinks, and run <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?ldconfig+8+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">ldconfig</span>(8)</span></a>.</p>
</li>
<li>
<p>In your <code class="filename">PLIST</code>,
include only the <code class=
"filename">.la</code> file (this is a change from
previous behaviour).</p>
</li>
</ol>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="using-libtool" id=
"using-libtool"></a>13.3.2. Using libtool on
GNU packages that already support libtool</h3>
</div>
</div>
</div>
<p>Add <code class="varname">USE_LIBTOOL=yes</code> to
the package Makefile. This will override the package's
own libtool in most cases. For older libtool using
packages, libtool is made by ltconfig script during the
do-configure step; you can check the libtool script
location by doing <span><strong class="command">make
configure; find work*/ -name
libtool</strong></span>.</p>
<p><code class="varname">LIBTOOL_OVERRIDE</code>
specifies which libtool scripts, relative to
<code class="varname">WRKSRC</code>, to override. By
default, it is set to “<span class=
"quote">libtool */libtool */*/libtool</span>”. If
this does not match the location of the package's
libtool script(s), set it as appropriate.</p>
<p>If you do not need <code class="filename">*.a</code>
static libraries built and installed, then use
<code class="varname">SHLIBTOOL_OVERRIDE</code>
instead.</p>
<p>If your package makes use of the platform
independent library for loading dynamic shared objects,
that comes with libtool (libltdl), you should include
devel/libltdl/buildlink3.mk.</p>
<p>Some packages use libtool incorrectly so that the
package may not work or build in some circumstances.
Some of the more common errors are:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>The inclusion of a shared object (-module) as
a dependent library in an executable or library.
This in itself isn't a problem if one of two
things has been done:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>The shared object is named correctly,
i.e. <code class=
"filename">libfoo.la</code>, not
<code class="filename">foo.la</code></p>
</li>
<li>
<p>The -dlopen option is used when linking
an executable.</p>
</li>
</ol>
</div>
</li>
<li>
<p>The use of libltdl without the correct calls
to initialisation routines. The function
lt_dlinit() should be called and the macro
<code class=
"varname">LTDL_SET_PRELOADED_SYMBOLS</code>
included in executables.</p>
</li>
</ul>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="autoconf-automake" id=
"autoconf-automake"></a>13.3.3. GNU
Autoconf/Automake</h3>
</div>
</div>
</div>
<p>If a package needs GNU autoconf or automake to be
executed to regenerate the configure script and
Makefile.in makefile templates, then they should be
executed in a pre-configure target. Two Makefile
fragments are provided in <code class=
"filename">pkgsrc/mk/autoconf.mk</code> and
<code class="filename">pkgsrc/mk/automake.mk</code> to
help dealing with these tools. See comments in these
files for details.</p>
<p>For packages that need only autoconf:</p>
<pre class="programlisting">
AUTOCONF_REQD= 2.50 # if default version is not good enough
...
pre-configure:
cd ${WRKSRC}; ${AUTOCONF}
...
.include "../../mk/autoconf.mk"
</pre>
<p>and for packages that need automake and
autoconf:</p>
<pre class="programlisting">
AUTOMAKE_REQD= 1.7.1 # if default version is not good enough
...
pre-configure:
cd ${WRKSRC}; \
${ACLOCAL}; \
${AUTOHEADER}; \
${AUTOMAKE} -a --foreign -i; \
${AUTOCONF}
...
.include "../mk/automake.mk"
</pre>
<p>Packages which use GNU Automake will almost
certainly require GNU Make, but that's automatically
provided for you in <code class=
"filename">mk/automake.mk</code>.</p>
<p>There are times when the configure process makes
additional changes to the generated files, which then
causes the build process to try to re-execute the
automake sequence. This is prevented by touching
various files in the configure stage. If this causes
problems with your package you can set <code class=
"varname">AUTOMAKE_OVERRIDE=NO</code> in the package
Makefile.</p>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"building-considerations" id=
"building-considerations"></a>13.4. Building
considerations</h2>
</div>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="cpp-defines" id=
"cpp-defines"></a>13.4.1. CPP defines</h3>
</div>
</div>
</div>
<p>To port an application to NetBSD, it's usually
necessary for the compiler to be able to judge the
system on which it's compiling, and we use definitions
so that the C pre-processor can do this.</p>
<p>To test whether you are working on a 4.4 BSD-derived
system, you should use the BSD definition, which is
defined in <code class=
"filename"><sys/param.h></code> on said
systems.</p>
<pre class="programlisting">
#include <sys/param.h>
</pre>
<p>and then you can surround the BSD-specific parts of
your package's C/C++ code using this conditional:</p>
<pre class="programlisting">
#if (defined(BSD) && BSD >= 199306)
...
#endif
</pre>
<p>Please use the “<span class=
"quote">__NetBSD__</span>” definition sparingly -
it should only apply to features of NetBSD that are not
present in other 4.4-lite derived BSDs.</p>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"package-specific-actions" id=
"package-specific-actions"></a>13.5. Package
specific actions</h2>
</div>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"package-configuration-files" id=
"package-configuration-files"></a>13.5.1. Package
configuration files</h3>
</div>
</div>
</div>
<p>Packages should be taught to look for their
configuration files in <code class=
"varname">${PKG_SYSCONFDIR}</code>, which is passed
through to the configure and build processes.
<code class="varname">PKG_SYSCONFDIR</code> may be
customized in various ways by setting other make
variables:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><code class="varname">PKG_SYSCONFBASE</code>
is the main config directory under which all
package configuration files are to be found. This
defaults to <code class=
"filename">${PREFIX}/etc</code>, but may be
overridden in <code class=
"filename">/etc/mk.conf</code>.</p>
</li>
<li>
<p><code class="varname">PKG_SYSCONFSUBDIR</code>
is the subdirectory of <code class=
"varname">PKG_SYSCONFBASE</code> under which the
configuration files for a particular package may
be found, e.g. the Apache configuration files may
all be found under the <code class=
"filename">httpd/</code> subdirectory of
<code class="varname">${PKG_SYSCONFBASE}</code>.
This should be set in the package Makefile.</p>
</li>
<li>
<p>By default, <code class=
"varname">PKG_SYSCONFDIR</code> is set to
<code class=
"varname">${PKG_SYSCONFBASE}/${PKG_SYSCONFSUBDIR}</code>,
but this may be overridden by setting
<code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code>
for a particular package, where <code class=
"varname">PKG_SYSCONFVAR</code> defaults to
<code class="varname">${PKGBASE}</code>. This is
not meant to be set by a package Makefile, but is
reserved for users who wish to override the
<code class="varname">PKG_SYSCONFDIR</code>
setting for a particular package with a special
location.</p>
</li>
</ul>
</div>
<p>The only variables that users should customize are
<code class="varname">PKG_SYSCONFBASE</code> and
<code class=
"varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code>.
Users will typically want to set <code class=
"varname">PKG_SYSCONFBASE</code> to <code class=
"filename">/etc</code>, or to accept the default
location of <code class=
"filename">${PREFIX}/etc</code>.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="user-interaction" id=
"user-interaction"></a>13.5.2. User
interaction</h3>
</div>
</div>
</div>
<p>Occasionally, packages require interaction from the
user, and this can be in a number of ways:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>help in fetching the distfiles</p>
</li>
<li>
<p>help to configure the package before it is
built</p>
</li>
<li>
<p>help during the build process</p>
</li>
<li>
<p>help during the installation of a package</p>
</li>
</ul>
</div>
<p>The <code class="varname">INTERACTIVE_STAGE</code>
definition is provided to notify the pkgsrc mechanism
of an interactive stage which will be needed, and this
should be set in the package's <code class=
"filename">Makefile</code>. e.g.</p>
<pre class="programlisting">
INTERACTIVE_STAGE= build
</pre>
<p>Multiple interactive stages can be specified:</p>
<pre class="programlisting">
INTERACTIVE_STAGE= configure install
</pre>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="handling-licenses" id=
"handling-licenses"></a>13.5.3. Handling
licenses</h3>
</div>
</div>
</div>
<p>A package may underly a license which the user has
or has not agreed to accept. Usually, packages that
underly well-known Open Source licenses (e.g. the GNU
Public License, GPL) won't have any special license
tags added in pkgsrc which require special action by
the user of such packages, but there are quite a number
of other licenses out there that pkgsrc users may not
be able to follow, for whatever reasons. For these
cases, pkgsrc contains a mechanism to note that a
package underlies a certain license, and the user has
to accept the license before the package can be
installed.</p>
<p>Placing a certain package under a certain license
works by setting the <code class=
"varname">LICENSE</code> variable to a string
identifying the license, e.g. in <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/graphics/graphviz/README.html"
class="pkgname">graphics/graphviz</a>:</p>
<pre class="programlisting">
LICENSE= graphviz-license
</pre>
<p>When trying to build, the user will get a notice
that the package underlies a license which he hasn't
accepted (yet):</p>
<pre class="programlisting">
<code class="prompt">%</code> <strong class=
"userinput"><code>make</code></strong>
===> graphviz-1.12 has an unacceptable license: graphviz-license.
===> To build this package, add this line to your /etc/mk.conf:
===> ACCEPTABLE_LICENSES+=graphviz-license
===> To view the license, enter "/usr/bin/make show-license".
*** Error code 1
</pre>
<p>The license can be viewed with <span><strong class=
"command">make show-license</strong></span>, and if it
is considered appropriate, the line printed above can
be added to <code class="filename">/etc/mk.conf</code>
to indicate acceptance of the particular license:</p>
<pre class="programlisting">
ACCEPTABLE_LICENSES+=graphviz-license
</pre>
<p>When adding a package with a new license, the
license text should be added to <code class=
"filename">pkgsrc/licenses</code> for displaying. A
list of known licenses can be seen in this directory as
well as by looking at the list of (commented out)
<code class="varname">ACCEPTABLE_LICENSES</code>
variable settings in <code class=
"filename">pkgsrc/mk/defaults/mk.conf</code>.</p>
<p>If there is a <span class=
"emphasis"><em>really</em></span> pressing need to
accept all licenses at once, like when trying to
download or mirror all distfiles or doing a bulk build
to test if all packages in pkgsrc build, this can be
done by setting <code class=
"varname">_ACCEPTABLE=yes</code>.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="creating-accounts" id=
"creating-accounts"></a>13.5.4. Creating an
account from a package</h3>
</div>
</div>
</div>
<p>There are two make variables used to control the
creation of package-specific groups and users at
pre-install time. The first is <code class=
"varname">PKG_GROUPS</code>, which is a list of
group[:groupid] elements, where the groupid is
optional. The second is <code class=
"varname">PKG_USERS</code>, which is a list of elements
of the form:</p>
<pre class="programlisting">
user:group[:[userid][:[description][:[home][:shell]]]]
</pre>
<p>where only the user and group are required, the rest
being optional. A simple example is:</p>
<pre class="programlisting">
PKG_GROUPS= foogroup
PKG_USERS= foouser:foogroup
</pre>
<p>A more complex example is that creates two groups
and two users is:</p>
<pre class="programlisting">
PKG_GROUPS= group1 group2:1005
PKG_USERS= first:group1::First\\ User \
second:group2::Second\\ User:/home/second:${SH}
</pre>
<p>By default, a new user will have home directory
<code class="filename">/nonexistent</code>, and login
shell <code class="filename">/sbin/nologin</code>
unless they are specified as part of the user
element.</p>
<p>The package <code class="filename">Makefile</code>
must also set <code class=
"varname">USE_PKGINSTALL=YES</code>. This will cause
the users and groups to be created at pre-install time,
and the admin will be prompted to remove them at
post-deinstall time. Automatic creation of the users
and groups can be toggled on and off by setting the
<code class="varname">PKG_CREATE_USERGROUP</code>
variable prior to package installation.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"installing-score-files" id=
"installing-score-files"></a>13.5.5. Installing
score files</h3>
</div>
</div>
</div>
<p>Certain packages, most of them in the games
category, install a score file that allows all users on
the system to record their highscores. In order for
this to work, the binaries need to be installed setgid
and the score files owned by the appropriate group
and/or owner (traditionally the "games" user/group).
The following variables, documented in more detail in
<code class="filename">mk/defaults/mk.conf</code>,
control this behaviour: <code class=
"varname">SETGIDGAME</code>, <code class=
"varname">GAMEDATAMODE</code>, <code class=
"varname">GAMEGRP</code>, <code class=
"varname">GAMEMODE</code>, <code class=
"varname">GAMEOWN</code>.</p>
<p>Note that per default, setgid installation of games
is disabled; setting <code class=
"varname">SETGIDGAME=YES</code> will set all the other
variables accordingly.</p>
<p>A package should therefor never hard code file
ownership or access permissions but rely on
<code class="varname">INSTALL_GAME</code> and
<code class="varname">INSTALL_GAME_DATA</code> to set
these correctly.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="login-shells" id=
"login-shells"></a>13.5.6. Packages
providing login shells</h3>
</div>
</div>
</div>
<p>If the purpose of the package is to provide a login
shell, the variable <code class=
"varname">PKG_SHELL</code> should contain the full
pathname of the shell executable installed by this
package. The package <code class=
"filename">Makefile</code> must also set <code class=
"varname">USE_PKGINSTALL=YES</code> to use the
automatically generated <code class=
"filename">INSTALL</code>/<code class=
"filename">DEINSTALL</code> scripts.</p>
<p>An example taken from shells/zsh:</p>
<pre class="programlisting">
USE_PKGINSTALL= YES
PKG_SHELL= ${PREFIX}/bin/zsh
</pre>
<p>The shell is registered into <code class=
"filename">/etc/shells</code> file automatically in the
post-install target by the generated <code class=
"filename">INSTALL</code> script and removed in the
deinstall target by the <code class=
"filename">DEINSTALL</code> script.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="perl-scripts" id=
"perl-scripts"></a>13.5.7. Packages
containing perl scripts</h3>
</div>
</div>
</div>
<p>If your package contains interpreted perl scripts,
set <code class="varname">REPLACE_PERL</code> to ensure
that the proper interpreter path is set. <code class=
"varname">REPLACE_PERL</code> should contain a list of
scripts, relative to <code class=
"varname">WRKSRC</code>, that you want adjusted.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="hardcoded-paths" id=
"hardcoded-paths"></a>13.5.8. Packages with
hardcoded paths to other interpreters</h3>
</div>
</div>
</div>
<p>Your package may also contain scripts with hardcoded
paths to other interpreters besides (or as well as)
perl. To correct the full pathname to the script
interpreter, you need to set the following definitions
in your <code class="filename">Makefile</code> (we
shall use <span><strong class=
"command">tclsh</strong></span> in this example):</p>
<pre class="programlisting">
REPLACE_INTERPRETER+= tcl
_REPLACE.tcl.old= .*/bin/tclsh
_REPLACE.tcl.new= ${PREFIX}/bin/tclsh
_REPLACE_FILES.tcl= ...list of tcl scripts which need to be fixed,
relative to ${WRKSRC}, just as in REPLACE_PERL
</pre>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="perl-modules" id=
"perl-modules"></a>13.5.9. Packages
installing perl modules</h3>
</div>
</div>
</div>
<p>Makefiles of packages providing perl5 modules should
include the Makefile fragment <code class=
"filename">../../lang/perl5/module.mk</code>. It
provides a <span><strong class=
"command">do-configure</strong></span> target for the
standard perl configuration for such modules as well as
various hooks to tune this configuration. See comments
in this file for details.</p>
<p>Perl5 modules will install into different places
depending on the version of perl used during the build
process. To address this, pkgsrc will append lines to
the <code class="filename">PLIST</code> corresponding
to the files listed in the installed <code class=
"filename">.packlist</code> file generated by most
perl5 modules. This is invoked by defining <code class=
"varname">PERL5_PACKLIST</code> to a space-separated
list of paths to packlist files, e.g.:</p>
<pre class="programlisting">
PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist
</pre>
<p>The variables <code class=
"varname">PERL5_SITELIB</code>, <code class=
"varname">PERL5_SITEARCH</code>, and <code class=
"varname">PERL5_ARCHLIB</code> represent the three
locations in which perl5 modules may be installed, and
may be used by perl5 packages that don't have a
packlist. These three variables are also substituted
for in the <code class="filename">PLIST</code>.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="faq.info-files" id=
"faq.info-files"></a>13.5.10. Packages
installing info files</h3>
</div>
</div>
</div>
<p>Some packages install info files or use the
“<span class="quote">makeinfo</span>” or
“<span class="quote">install-info</span>”
commands. Each of the info files:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>is considered to be installed in the directory
<code class=
"filename">${PREFIX}/${INFO_DIR}</code>,</p>
</li>
<li>
<p>is registered in the Info directory file
<code class=
"filename">${PREFIX}/${INFO_DIR}/dir</code>,</p>
</li>
<li>
<p>and must be listed as a filename in the
<code class="varname">INFO_FILES</code> variable
in the package Makefile.</p>
</li>
</ul>
</div>
<p><code class="varname">INFO_DIR</code> defaults to
“<span class="quote">info</span>” and can
be overridden in the package Makefile. <code class=
"filename">INSTALL</code> and <code class=
"filename">DEINSTALL</code> scripts will be generated
to handle registration of the info files in the Info
directory file. The “<span class=
"quote">install-info</span>” command used for the
info files registration is either provided by the
system, or by a special purpose package automatically
added as dependency if needed.</p>
<p>A package which needs the “<span class=
"quote">makeinfo</span>” command at build time
must define the variable <code class=
"varname">USE_MAKEINFO</code> in its Makefile. If a
minimum version of the “<span class=
"quote">makeinfo</span>” command is needed it
should be noted with the <code class=
"varname">TEXINFO_REQD</code> variable in the package
<code class="filename">Makefile</code>. By default, a
minimum version of 3.12 is required. If the system does
not provide a <span><strong class=
"command">makeinfo</strong></span> command or if it
does not match the required minimum, a build dependency
on the <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/gtexinfo/README.html"
class="pkgname">devel/gtexinfo</a> package will be
added automatically.</p>
<p>The build and installation process of the software
provided by the package should not use the
<span><strong class=
"command">install-info</strong></span> command as the
registration of info files is the task of the package
<code class="filename">INSTALL</code> script, and it
must use the appropriate <span><strong class=
"command">makeinfo</strong></span> command.</p>
<p>To achieve this goal the pkgsrc infrastructure
creates overriding scripts for the <span><strong class=
"command">install-info</strong></span> and
<span><strong class="command">makeinfo</strong></span>
commands in a directory listed early in <code class=
"varname">PATH</code>.</p>
<p>The script overriding <span><strong class=
"command">install-info</strong></span> has no effect
except the logging of a message. The script overriding
<span><strong class="command">makeinfo</strong></span>
logs a message and according to the value of
<code class="varname">USE_MAKEINFO</code> and
<code class="varname">TEXINFO_REQD</code> either run
the appropriate <span><strong class=
"command">makeinfo</strong></span> command or exit on
error.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="gconf2-data-files" id=
"gconf2-data-files"></a>13.5.11. Packages
installing GConf2 data files</h3>
</div>
</div>
</div>
<p>If a package installs <code class=
"filename">.schemas</code> or <code class=
"filename">.entries</code> files, used by GConf2, you
need to take some extra steps to make sure they get
registered in the database:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>Include <code class=
"filename">../../devel/GConf2/schemas.mk</code>
instead of its <code class=
"filename">buildlink3.mk</code> file. This takes
care of rebuilding the GConf2 database at
installation and deinstallation time, and tells
the package where to install GConf2 data files
using some standard configure arguments. It also
disallows any access to the database directly
from the package.</p>
</li>
<li>
<p>Ensure that the package installs its
<code class="filename">.schemas</code> files
under <code class=
"filename">${PREFIX}/share/gconf/schemas</code>.
If they get installed under <code class=
"filename">${PREFIX}/etc</code>, you will need to
manually patch the package.</p>
</li>
<li>
<p>Check the PLIST and remove any entries under
the etc/gconf directory, as they will be handled
automatically. See <a href="#faq.conf" title=
"6.14. Configuration files handling and placement">
Section 6.14, “Configuration files
handling and placement”</a> for more
information.</p>
</li>
<li>
<p>Define the <code class=
"varname">GCONF2_SCHEMAS</code> variable in your
<code class="filename">Makefile</code> with a
list of all <code class=
"filename">.schemas</code> files installed by the
package, if any. Names must not contain any
directories in them.</p>
</li>
<li>
<p>Define the <code class=
"varname">GCONF2_ENTRIES</code> variable in your
<code class="filename">Makefile</code> with a
list of all <code class=
"filename">.entries</code> files installed by the
package, if any. Names must not contain any
directories in them.</p>
</li>
</ol>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"scrollkeeper-data-files" id=
"scrollkeeper-data-files"></a>13.5.12. Packages
installing scrollkeeper data files</h3>
</div>
</div>
</div>
<p>If a package installs <code class=
"filename">.omf</code> files, used by scrollkeeper, you
need to take some extra steps to make sure they get
registered in the database:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>Include <code class=
"filename">../../textproc/scrollkeeper/omf.mk</code>
instead of its <code class=
"filename">buildlink3.mk</code> file. This takes
care of rebuilding the scrollkeeper database at
installation and deinstallation time, and
disallows any access to it directly from the
package.</p>
</li>
<li>
<p>Check the PLIST and remove any entries under
the <code class=
"filename">libdata/scrollkeeper</code> directory,
as they will be handled automatically.</p>
</li>
<li>
<p>Remove the <code class=
"filename">share/omf</code> directory from the
PLIST. It will be handled by scrollkeeper.</p>
</li>
</ol>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="x11-fonts" id=
"x11-fonts"></a>13.5.13. Packages installing
X11 fonts</h3>
</div>
</div>
</div>
<p>If a package installs font files, you will need to
rebuild the fonts database in the directory where they
get installed at installation and deinstallation time.
This can be automatically done by using <code class=
"filename">mk/fonts.mk</code>, which you need to
include in your <code class=
"filename">Makefile</code>.</p>
<p>When the file is included, you can list the
directories where fonts are installed in the
<code class="varname">FONTS_<em class=
"replaceable"><code>type</code></em>_DIRS</code>
variables, where <em class=
"replaceable"><code>type</code></em> can be one of
“<span class="quote">TTF</span>”,
“<span class="quote">TYPE1</span>” or
“<span class="quote">X11</span>”. Also make
sure that the database file <code class=
"filename">fonts.dir</code> is not listed in the
PLIST.</p>
<p>Note that you should not create new directories for
fonts; instead use the standard ones to avoid that the
user needs to manually configure his X server to find
them.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="gtk2-modules" id=
"gtk2-modules"></a>13.5.14. Packages
installing GTK2 modules</h3>
</div>
</div>
</div>
<p>If a package installs gtk2 immodules or loaders, you
need to take some extra steps to get them registered in
the GTK2 database properly:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>Include <code class=
"filename">../../x11/gtk2/modules.mk</code>
instead of its <code class=
"filename">buildlink3.mk</code> file. This takes
care of rebuilding the database at installation
and deinstallation time.</p>
</li>
<li>
<p>Set <code class=
"varname">GTK2_IMMODULES=YES</code> if your
package installs GTK2 immodules.</p>
</li>
<li>
<p>Set <code class=
"varname">GTK2_LOADERS=YES</code> if your package
installs GTK2 loaders.</p>
</li>
<li>
<p>Patch the package to not touch any of the gtk2
databases directly. These are:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><code class=
"filename">libdata/gtk-2.0/gdk-pixbuf.loaders</code></p>
</li>
<li>
<p><code class=
"filename">libdata/gtk-2.0/gtk.immodules</code></p>
</li>
</ul>
</div>
</li>
<li>
<p>Check the PLIST and remove any entries under
the <code class="filename">libdata/gtk-2.0</code>
directory, as they will be handled
automatically.</p>
</li>
</ol>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="sgml-xml-data" id=
"sgml-xml-data"></a>13.5.15. Packages
installing SGML or XML data</h3>
</div>
</div>
</div>
<p>If a package installs SGML or XML data files that
need to be registered in system-wide catalogs (like
DTDs, sub-catalogs, etc.), you need to take some extra
steps:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>Include <code class=
"filename">../../textproc/xmlcatmgr/catalogs.mk</code>
in your <code class="filename">Makefile</code>,
which takes care of registering those files in
system-wide catalogs at installation and
deinstallation time.</p>
</li>
<li>
<p>Set <code class="varname">SGML_CATALOGS</code>
to the full path of any SGML catalogs installed
by the package.</p>
</li>
<li>
<p>Set <code class="varname">XML_CATALOGS</code>
to the full path of any XML catalogs installed by
the package.</p>
</li>
<li>
<p>Set <code class="varname">SGML_ENTRIES</code>
to individual entries to be added to the SGML
catalog. These come in groups of three strings;
see xmlcatmgr(1) for more information
(specifically, arguments recognized by the 'add'
action). Note that you will normally not use this
variable.</p>
</li>
<li>
<p>Set <code class="varname">XML_ENTRIES</code>
to individual entries to be added to the XML
catalog. These come in groups of three strings;
see xmlcatmgr(1) for more information
(specifically, arguments recognized by the 'add'
action). Note that you will normally not use this
variable.</p>
</li>
</ol>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="mime-database" id=
"mime-database"></a>13.5.16. Packages
installing extensions to the MIME database</h3>
</div>
</div>
</div>
<p>If a package provides extensions to the MIME
database by installing <code class=
"filename">.xml</code> files inside <code class=
"filename">${PREFIX}/share/mime/packages</code>, you
need to take some extra steps to ensure that the
database is kept consistent with respect to these new
files:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>Include <code class=
"filename">../../databases/shared-mime-info/mimedb.mk</code>
(avoid using the <code class=
"filename">buildlink3.mk</code> file from this
same directory, which is reserved for inclusion
from other <code class=
"filename">buildlink3.mk</code> files). It takes
care of rebuilding the MIME database at
installation and deinstallation time, and
disallows any access to it directly from the
package.</p>
</li>
<li>
<p>Check the PLIST and remove any entries under
the <code class="filename">share/mime</code>
directory, <span class=
"emphasis"><em>except</em></span> for files saved
under <code class=
"filename">share/mime/packages</code>. The former
are handled automatically by the
update-mime-database program, but the later are
package-dependent and must be removed by the
package that installed them in the first
place.</p>
</li>
<li>
<p>Remove any <code class=
"filename">share/mime/*</code> directories from
the PLIST. They will be handled by the
shared-mime-info package.</p>
</li>
</ol>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="intltool" id=
"intltool"></a>13.5.17. Packages using
intltool</h3>
</div>
</div>
</div>
<p>If a package uses intltool during its build, include
the <code class=
"filename">../../textproc/intltool/buildlink3.mk</code>
file, which forces it to use the intltool package
provided by pkgsrc, instead of the one bundled with the
distribution file.</p>
<p>This tracks intltool's build-time dependencies and
uses the latest available version; this way, the
package benefits of any bug fixes that may have
appeared since it was released.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="startup-scripts" id=
"startup-scripts"></a>13.5.18. Packages
installing startup scripts</h3>
</div>
</div>
</div>
<p>If a package contains a rc.d script, it won't be
copied into the startup directory by default, but you
can enable it, by adding the option <code class=
"varname">PKG_RCD_SCRIPTS=YES</code> in <code class=
"filename">/etc/mk.conf</code>. This option will copy
the scripts into <code class=
"filename">/etc/rc.d</code> when a package is
installed, and it will automatically remove the scripts
when the package is deinstalled.</p>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"feedback-to-author" id=
"feedback-to-author"></a>13.6. Feedback to the
author</h2>
</div>
</div>
</div>
<p>If you have found any bugs in the package you make
available, if you had to do special steps to make it run
under NetBSD or if you enhanced the software in various
other ways, be sure to report these changes back to the
original author of the program! With that kind of
support, the next release of the program can incorporate
these fixes, and people not using the NetBSD packages
system can win from your efforts.</p>
<p>Support the idea of free software!</p>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="debug" id=
"debug"></a>Chapter 14. Debugging</h2>
</div>
</div>
</div>
<p>To check out all the gotchas when building a package,
here are the steps that I do in order to get a package
working. Please note this is basically the same as what was
explained in the previous sections, only with some
debugging aids.</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>Be sure to set <code class=
"varname">PKG_DEVELOPER=1</code> in <code class=
"filename">/etc/mk.conf</code></p>
</li>
<li>
<p>Install <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/url2pkg/README.html"
class="pkgname">pkgtools/url2pkg</a>, create a
directory for a new package, change into it, then run
<span><strong class=
"command">url2pkg</strong></span>:</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>mkdir /usr/pkgsrc/<em class=
"replaceable"><code>category</code></em>/<em class=
"replaceable"><code>examplepkg</code></em></code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>cd /usr/pkgsrc/<em class=
"replaceable"><code>category</code></em>/<em class=
"replaceable"><code>examplepkg</code></em></code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>url2pkg http://www.example.com/path/to/distfile.tar.gz</code></strong>
</pre>
</li>
<li>
<p>Edit the <code class="filename">Makefile</code> as
requested.</p>
</li>
<li>
<p>Fill in the <code class="filename">DESCR</code>
file</p>
</li>
<li>
<p>Run <span><strong class="command">make
configure</strong></span></p>
</li>
<li>
<p>Add any dependencies glimpsed from documentation
and the configure step to the package's <code class=
"filename">Makefile</code>.</p>
</li>
<li>
<p>Make the package compile, doing multiple rounds
of</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>make</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>pkgvi ${WRKSRC}/some/file/that/does/not/compile</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>mkpatches</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>patchdiff</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>mv ${WRKDIR}/.newpatches/* patches</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>make mps</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>make clean</code></strong>
</pre>
<p>Doing as non-root user will ensure that no files
are modified that shouldn't be, especially during the
build phase. <span><strong class=
"command">mkpatches</strong></span>,
<span><strong class=
"command">patchdiff</strong></span> and
<span><strong class="command">pkgvi</strong></span>
are from the <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdiff/README.html"
class="pkgname">pkgtools/pkgdiff</a> package.</p>
</li>
<li>
<p>Look at the <code class=
"filename">Makefile</code>, fix if necessary; see
<a href="#components.Makefile" title=
"7.1. Makefile">Section 7.1,
“<code class=
"filename">Makefile</code>”</a>.</p>
</li>
<li>
<p>Generate a <code class=
"filename">PLIST</code>:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make install</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>make print-PLIST >PLIST</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>make deinstall</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>make install</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>make deinstall</code></strong>
</pre>
<p>You usually need to be <code class=
"username">root</code> to do this. Look if there are
any files left:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make print-PLIST</code></strong>
</pre>
<p>If this reveals any files that are missing in
<code class="filename">PLIST</code>, add them.</p>
</li>
<li>
<p>Now that the <code class="filename">PLIST</code>
is OK, install the package again and make a binary
package:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make reinstall</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>make package</code></strong>
</pre>
</li>
<li>
<p>Delete the installed package:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>pkg_delete blub</code></strong>
</pre>
</li>
<li>
<p>Repeat the above <span><strong class=
"command">make print-PLIST</strong></span> command,
which shouldn't find anything now:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make print-PLIST</code></strong>
</pre>
</li>
<li>
<p>Reinstall the binary package:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>pkgadd .../blub.tgz</code></strong>
</pre>
</li>
<li>
<p>Play with it. Make sure everything works.</p>
</li>
<li>
<p>Run <span><strong class=
"command">pkglint</strong></span> from <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkglint/README.html"
class="pkgname">pkgtools/pkglint</a>, and fix the
problems it reports:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>pkglint</code></strong>
</pre>
</li>
<li>
<p>Submit (or commit, if you have cvs access); see
<a href="#submit" title=
"Chapter 15. Submitting and Committing">Chapter 15,
<i>Submitting and Committing</i></a>.</p>
</li>
</ul>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="submit" id=
"submit"></a>Chapter 15. Submitting and
Committing</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href=
"#submitting-your-package">15.1. Submitting your
packages</a></span></dt>
<dt><span class="sect1"><a href=
"#committing-importing">15.2. Committing: Importing a
package into CVS</a></span></dt>
<dt><span class="sect1"><a href=
"#updating-package">15.3. Updating a package to a newer
version</a></span></dt>
<dt><span class="sect1"><a href="#moving-package">15.4.
Moving a package in pkgsrc</a></span></dt>
</dl>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"submitting-your-package" id=
"submitting-your-package"></a>15.1. Submitting
your packages</h2>
</div>
</div>
</div>
<p>You have to separate between binary and
“<span class="quote">normal</span>” (source)
packages here:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>precompiled binary packages</p>
<p>Our policy is that we accept binaries only from
pkgsrc developers to guarantee that the packages
don't contain any trojan horses etc. This is not to
annoy anyone but rather to protect our users!
You're still free to put up your home-made binary
packages and tell the world where to get them.
NetBSD developers doing bulk builds and wanting to
upload them please see <a href="#bulk-upload"
title="5.3.8. Uploading results of a bulk build">
Section 5.3.8, “Uploading results of a
bulk build”</a>.</p>
</li>
<li>
<p>packages</p>
<p>First, check that your package is complete,
compiles and runs well; see <a href="#debug" title=
"Chapter 14. Debugging">Chapter 14,
<i>Debugging</i></a> and the rest of this document.
Next, generate an uuencoded gzipped <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?tar+1+NetBSD-current">
<span class="citerefentry"><span class=
"refentrytitle">tar</span>(1)</span></a> archive,
preferably with all files in a single directory.
Finally, <span><strong class=
"command">send-pr</strong></span> with category
“<span class="quote">pkg</span>”, a
synopsis which includes the package name and
version number, a short description of your package
(contents of the COMMENT variable or DESCR file are
OK) and attach the archive to your PR.</p>
<p>If you want to submit several packages, please
send a separate PR for each one, it's easier for us
to track things that way.</p>
<p>Alternatively, you can also import new packages
into pkgsrc-wip (“<span class="quote">pkgsrc
work-in-progress</span>”); see the homepage
at <a href="http://pkgsrc-wip.sourceforge.net/"
target=
"_top">http://pkgsrc-wip.sourceforge.net/</a> for
details.</p>
</li>
</ul>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"committing-importing" id=
"committing-importing"></a>15.2. Committing:
Importing a package into CVS</h2>
</div>
</div>
</div>
<p>This section is only of interest for pkgsrc developers
with write access to the pkgsrc repository. Please
remember that cvs imports files relative to the current
working directory, and that the pathname that you give
the <span><strong class="command">cvs
import</strong></span> command is so that it knows where
to place the files in the repository. Newly created
packages should be imported with a vendor tag of
“<span class="quote">TNF</span>” and a
release tag of “<span class=
"quote">pkgsrc-base</span>”, e.g:</p>
<pre class="programlisting">
% cd .../pkgsrc/category/pkgname
% cvs import pkgsrc/category/pkgname TNF pkgsrc-base
</pre>
<p>Remember to move the directory from which you imported
out of the way, or cvs will complain the next time you
“<span class="quote">cvs update</span>” your
source tree. Also don't forget to add the new package to
the category's <code class=
"filename">Makefile</code>.</p>
<p>The commit message of the initial import should
include part of the <code class="filename">DESCR</code>
file, so people reading the mailing lists know what the
package is/does.</p>
<p>Please note all package updates/additions in
<code class="filename">pkgsrc/doc/CHANGES</code>. It's
very important to keep this file up to date and
conforming to the existing format, because it will be
used by scripts to automatically update pages on <a href=
"http://www.NetBSD.org/" target="_top">www.NetBSD.org</a>
and other sites. Additionally, check the pkgsrc/doc/TODO
file and remove the entry for the package you updated, in
case it was mentioned there.</p>
<p>For new packages, “<span class="quote">cvs
import</span>” is preferred to “<span class=
"quote">cvs add</span>” because the former gets
everything with a single command, and provides a
consistent tag.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"updating-package" id=
"updating-package"></a>15.3. Updating a
package to a newer version</h2>
</div>
</div>
</div>
<p>Please always put a concise, appropriate and relevant
summary of the changes between old and new versions into
the commit log when updating a package. There are various
reasons for this:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>A URL is volatile, and can change over time. It
may go away completely or its information may be
overwritten by newer information.</p>
</li>
<li>
<p>Having the change information between old and
new versions in our CVS repository is very useful
for people who use either cvs or anoncvs.</p>
</li>
<li>
<p>Having the change information between old and
new versions in our CVS repository is very useful
for people who read the pkgsrc-changes mailing
list, so that they can make tactical decisions
about when to upgrade the package.</p>
</li>
</ul>
</div>
<p>Please also recognize that, just because a new version
of a package has been released, it should not
automatically be upgraded in the CVS repository. We
prefer to be conservative in the packages that are
included in pkgsrc - development or beta packages are not
really the best thing for most places in which pkgsrc is
used. Please use your judgement about what should go into
pkgsrc, and bear in mind that stability is to be
preferred above new and possibly untested features.</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"moving-package" id=
"moving-package"></a>15.4. Moving a package in
pkgsrc</h2>
</div>
</div>
</div>
<div class="orderedlist">
<ol type="1">
<li>
<p>Make a copy of the directory somewhere else.</p>
</li>
<li>
<p>Remove all CVS dirs.</p>
<p>Alternatively to the first two steps you can
also do:</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>cvs -d user@cvs.NetBSD.org:/cvsroot export -D today pkgsrc/category/package</code></strong>
</pre>
<p>and use that for further work.</p>
</li>
<li>
<p>Fix <code class="varname">CATEGORIES</code> and
any <code class="varname">DEPENDS</code> paths that
just did “<span class=
"quote">../package</span>” instead of
“<span class=
"quote">../../category/package</span>”.</p>
</li>
<li>
<p><span><strong class="command">cvs
import</strong></span> the modified package in the
new place.</p>
</li>
<li>
<p>Check if any package depends on it:</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>cd /usr/pkgsrc</code></strong>
<code class="prompt">%</code> <strong class=
"userinput"><code>grep /package */*/Makefile* */*/buildlink*</code></strong>
</pre>
</li>
<li>
<p>Fix paths in packages from step 5 to point to
new location.</p>
</li>
<li>
<p><span><strong class="command">cvs rm
(-f)</strong></span> the package at the old
location.</p>
</li>
<li>
<p>Remove from <code class=
"filename">oldcategory/Makefile</code>.</p>
</li>
<li>
<p>Add to <code class=
"filename">newcategory/Makefile</code>.</p>
</li>
<li>
<p>Commit the changed and removed files:</p>
<pre class="screen">
<code class="prompt">%</code> <strong class=
"userinput"><code>cvs commit oldcategory/package oldcategory/Makefile newcategory/Makefile</code></strong>
</pre>
<p>(and any packages from step 5, of course).</p>
</li>
</ol>
</div>
</div>
</div>
</div>
<div class="appendix" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="examples" id=
"examples"></a>Appendix A. A simple example
package: bison</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href="#example-files">A.1.
files</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
"#example-Makefile">A.1.1. Makefile</a></span></dt>
<dt><span class="sect2"><a href=
"#example-descr">A.1.2. DESCR</a></span></dt>
<dt><span class="sect2"><a href=
"#example-plist">A.1.3. PLIST</a></span></dt>
<dt><span class="sect2"><a href=
"#checking-package-with-pkglint">A.1.4. Checking a
package with <span><strong class=
"command">pkglint</strong></span></a></span></dt>
</dl>
</dd>
<dt><span class="sect1"><a href="#steps-for-b-i-p">A.2.
Steps for building, installing, packaging</a></span></dt>
</dl>
</div>
<p>We checked to find a piece of software that wasn't in the
packages collection, and picked GNU bison. Quite why someone
would want to have <span><strong class=
"command">bison</strong></span> when Berkeley
<span><strong class="command">yacc</strong></span> is already
present in the tree is beyond us, but it's useful for the
purposes of this exercise.</p>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"example-files" id=
"example-files"></a>A.1. files</h2>
</div>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="example-Makefile" id=
"example-Makefile"></a>A.1.1. Makefile</h3>
</div>
</div>
</div>
<pre class="programlisting">
# $NetBSD$
#
DISTNAME= bison-1.25
CATEGORIES= devel
MASTER_SITES= ${MASTER_SITE_GNU}
MAINTAINER= thorpej@NetBSD.org
HOMEPAGE= http://www.gnu.org/software/bison/bison.html
COMMENT= GNU yacc clone
GNU_CONFIGURE= yes
INFO_FILES= bison.info
.include "../../mk/bsd.pkg.mk"
</pre>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="example-descr" id=
"example-descr"></a>A.1.2. DESCR</h3>
</div>
</div>
</div>
<pre class="programlisting">
GNU version of yacc. Can make re-entrant parsers, and numerous other
improvements. Why you would want this when Berkeley <a href=
"http://netbsd.gw.com/cgi-bin/man-cgi?yacc+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">yacc</span>(1)</span></a> is part
of the NetBSD source tree is beyond me.
</pre>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="example-plist" id=
"example-plist"></a>A.1.3. PLIST</h3>
</div>
</div>
</div>
<pre class="programlisting">
@comment $NetBSD$
bin/bison
man/man1/bison.1.gz
share/bison.simple
share/bison.hairy
</pre>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name=
"checking-package-with-pkglint" id=
"checking-package-with-pkglint"></a>A.1.4. Checking
a package with <span><strong class=
"command">pkglint</strong></span></h3>
</div>
</div>
</div>
<p>The NetBSD package system comes with <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional" href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkglint/README.html"
class="pkgname">pkgtools/pkglint</a> which helps to check
the contents of these files. After installation it is
quite easy to use, just change to the directory of the
package you wish to examine and execute
<span><strong class=
"command">pkglint</strong></span>:</p>
<pre class="screen">
<code class="prompt">$</code> <strong class=
"userinput"><code>pkglint</code></strong>
looks fine.
</pre>
<p>Depending on the supplied command line arguments (see
pkglint(1)) more verbose checks will be performed. Use
e.g. <span><strong class="command">pkglint
-v</strong></span> for a very verbose check.</p>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"steps-for-b-i-p" id=
"steps-for-b-i-p"></a>A.2. Steps for building,
installing, packaging</h2>
</div>
</div>
</div>
<p>Create the directory where the package lives, plus any
auxiliary directories:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>cd /usr/pkgsrc/lang</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>mkdir bison</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>cd bison</code></strong>
<code class="prompt">#</code> <strong class=
"userinput"><code>mkdir patches</code></strong>
</pre>
<p>Create <code class="filename">Makefile</code>,
<code class="filename">DESCR</code> and <code class=
"filename">PLIST</code> (see <a href="#components" title=
"Chapter 7. Package components - files, directories and contents">
Chapter 7, <i>Package components - files, directories and
contents</i></a>) then continue with fetching the
distfile:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make fetch</code></strong>
>> bison-1.25.tar.gz doesn't seem to exist on this system.
>> Attempting to fetch from ftp://prep.ai.mit.edu/pub/gnu//.
Requesting ftp://prep.ai.mit.edu/pub/gnu//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
ftp: Error retrieving file: 500 Internal error
>> Attempting to fetch from ftp://wuarchive.wustl.edu/systems/gnu//.
Requesting ftp://wuarchive.wustl.edu/systems/gnu//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
ftp: Error retrieving file: 500 Internal error
>> Attempting to fetch from ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//.
Requesting ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
Successfully retrieved file.
</pre>
<p>Generate the checksum of the distfile into <code class=
"filename">distinfo</code>:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make makesum</code></strong>
</pre>
<p>Now compile:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make</code></strong>
>> Checksum OK for bison-1.25.tar.gz.
===> Extracting for bison-1.25
===> Patching for bison-1.25
===> Ignoring empty patch directory
===> Configuring for bison-1.25
creating cache ./config.cache
checking for gcc... cc
checking whether we are using GNU C... yes
checking for a BSD compatible install... /usr/bin/install -c -o bin -g bin
checking how to run the C preprocessor... cc -E
checking for minix/config.h... no
checking for POSIXized ISC... no
checking whether cross-compiling... no
checking for ANSI C header files... yes
checking for string.h... yes
checking for stdlib.h... yes
checking for memory.h... yes
checking for working const... yes
checking for working alloca.h... no
checking for alloca... yes
checking for strerror... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
===> Building for bison-1.25
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g LR0.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g allocate.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g closure.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g conflicts.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g derives.c
cc -c -DXPFILE=\"/usr/pkg/share/bison.simple\" -DXPFILE1=\"/usr/pkg/share/bison.hairy\" -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -g ./files.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g getargs.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g gram.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g lalr.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g lex.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g main.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g nullable.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g output.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g print.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g reader.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g reduce.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g symtab.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g warshall.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g version.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g getopt.c
cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g getopt1.c
cc -g -o bison LR0.o allocate.o closure.o conflicts.o derives.o files.o getargs.o gram.o lalr.o lex.o main.o nullable.o output.o print.o reader.o reduce.o symtab.o warshall.o version.o getopt.o getopt1.o
./files.c:240: warning: mktemp() possibly used unsafely, consider using mkstemp()
rm -f bison.s1
sed -e "/^#line/ s|bison|/usr/pkg/share/bison|" < ./bison.simple > bison.s1
</pre>
<p>Everything seems OK, so install the files:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make install</code></strong>
>> Checksum OK for bison-1.25.tar.gz.
===> Installing for bison-1.25
sh ./mkinstalldirs /usr/pkg/bin /usr/pkg/share /usr/pkg/info /usr/pkg/man/man1
rm -f /usr/pkg/bin/bison
cd /usr/pkg/share; rm -f bison.simple bison.hairy
rm -f /usr/pkg/man/man1/bison.1 /usr/pkg/info/bison.info*
install -c -o bin -g bin -m 555 bison /usr/pkg/bin/bison
/usr/bin/install -c -o bin -g bin -m 644 bison.s1 /usr/pkg/share/bison.simple
/usr/bin/install -c -o bin -g bin -m 644 ./bison.hairy /usr/pkg/share/bison.hairy
cd .; for f in bison.info*; do /usr/bin/install -c -o bin -g bin -m 644 $f /usr/pkg/info/$f; done
/usr/bin/install -c -o bin -g bin -m 644 ./bison.1 /usr/pkg/man/man1/bison.1
===> Registering installation for bison-1.25
</pre>
<p>You can now use bison, and also - if you decide so -
remove it with <span><strong class="command">pkg_delete
bison</strong></span>. Should you decide that you want a
binary package, do this now:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make package</code></strong>
>> Checksum OK for bison-1.25.tar.gz.
===> Building package for bison-1.25
Creating package bison-1.25.tgz
Registering depends:.
Creating gzip'd tar ball in '/u/pkgsrc/lang/bison/bison-1.25.tgz'
</pre>
<p>Now that you don't need the source and object files any
more, clean up:</p>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make clean</code></strong>
===> Cleaning for bison-1.25
</pre>
</div>
</div>
<div class="appendix" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="logs" id=
"logs"></a>Appendix B. Build logs</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href="#logs.building">B.1.
Building figlet</a></span></dt>
<dt><span class="sect1"><a href="#logs.package">B.2.
Packaging figlet</a></span></dt>
</dl>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"logs.building" id=
"logs.building"></a>B.1. Building figlet</h2>
</div>
</div>
</div>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make</code></strong>
===> Checking for vulnerabilities in figlet-2.2.1nb2
=> figlet221.tar.gz doesn't seem to exist on this system.
=> Attempting to fetch figlet221.tar.gz from ftp://ftp.figlet.org/pub/figlet/program/unix/.
=> [172219 bytes]
Connected to ftp.plig.net.
220 ftp.plig.org NcFTPd Server (licensed copy) ready.
331 Guest login ok, send your complete e-mail address as password.
230-You are user #5 of 500 simultaneous users allowed.
230-
230- ___ _ _ _
230- | _| |_ ___ ___| |_|___ ___ ___ ___
230- | _| _| . |_| . | | | . |_| . | _| . |
230- |_| |_| | _|_| _|_|_|_ |_|___|_| |_ |
230- |_| |_| |___| |___|
230-
230-** Welcome to ftp.plig.org **
230-
230-Please note that all transfers from this FTP site are logged. If you
230-do not like this, please disconnect now.
230-
230-This arhive is available via
230-
230-HTTP: http://ftp.plig.org/
230-FTP: ftp://ftp.plig.org/ (max 500 connections)
230-RSYNC: rsync://ftp.plig.org/ (max 30 connections)
230-
230-Please email comments, bug reports and requests for packages to be
230-mirrored to ftp-admin@plig.org.
230-
230-
230 Logged in anonymously.
Remote system type is UNIX.
Using binary mode to transfer files.
200 Type okay.
250 "/pub" is new cwd.
250-"/pub/figlet" is new cwd.
250-
250-Welcome to the figlet archive at ftp.figlet.org
250-
250- ftp://ftp.figlet.org/pub/figlet/
250-
250-The official FIGlet web page is:
250- http://www.figlet.org/
250-
250-If you have questions, please mailto:info@figlet.org. If you want to
250-contribute a font or something else, you can email us.
250
250 "/pub/figlet/program" is new cwd.
250 "/pub/figlet/program/unix" is new cwd.
local: figlet221.tar.gz remote: figlet221.tar.gz
502 Unimplemented command.
227 Entering Passive Mode (195,40,6,41,246,104)
150 Data connection accepted from 84.128.86.72:65131; transfer starting for figlet221.tar.gz (172219 bytes).
38% |************** | 65800 64.16 KB/s 00:01 ETA
226 Transfer completed.
172219 bytes received in 00:02 (75.99 KB/s)
221 Goodbye.
=> Checksum OK for figlet221.tar.gz.
===> Extracting for figlet-2.2.1nb2
===> Required installed package ccache-[0-9]*: ccache-2.3nb1 found
===> Patching for figlet-2.2.1nb2
===> Applying pkgsrc patches for figlet-2.2.1nb2
===> Overriding tools for figlet-2.2.1nb2
===> Creating toolchain wrappers for figlet-2.2.1nb2
===> Configuring for figlet-2.2.1nb2
===> Building for figlet-2.2.1nb2
gcc -O2 -DDEFAULTFONTDIR=\"/usr/pkg/share/figlet\" -DDEFAULTFONTFILE=\"standard.flf\" figlet.c zipio.c crc.c inflate.c -o figlet
chmod a+x figlet
gcc -O2 -o chkfont chkfont.c
=> Unwrapping files-to-be-installed.
<code class="prompt">#</code>
<code class="prompt">#</code> <strong class=
"userinput"><code>make install</code></strong>
===> Checking for vulnerabilities in figlet-2.2.1nb2
===> Installing for figlet-2.2.1nb2
install -d -o root -g wheel -m 755 /usr/pkg/bin
install -d -o root -g wheel -m 755 /usr/pkg/man/man6
mkdir -p /usr/pkg/share/figlet
cp figlet /usr/pkg/bin
cp chkfont /usr/pkg/bin
chmod 555 figlist showfigfonts
cp figlist /usr/pkg/bin
cp showfigfonts /usr/pkg/bin
cp fonts/*.flf /usr/pkg/share/figlet
cp fonts/*.flc /usr/pkg/share/figlet
cp figlet.6 /usr/pkg/man/man6
===> Registering installation for figlet-2.2.1nb2
<code class="prompt">#</code>
</pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"logs.package" id=
"logs.package"></a>B.2. Packaging figlet</h2>
</div>
</div>
</div>
<pre class="screen">
<code class="prompt">#</code> <strong class=
"userinput"><code>make package</code></strong>
===> Checking for vulnerabilities in figlet-2.2.1nb2
===> Packaging figlet-2.2.1nb2
===> Building binary package for figlet-2.2.1nb2
Creating package /home/cvs/pkgsrc/packages/i386/All/figlet-2.2.1nb2.tgz
Using SrcDir value of /usr/pkg
Registering depends:.
<code class="prompt">#</code>
</pre>
</div>
</div>
<div class="appendix" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="ftp-layout" id=
"ftp-layout"></a>Appendix C. Layout of the
FTP server's package archive</h2>
</div>
</div>
</div>
<p>Layout for precompiled binary packages on
ftp.NetBSD.org:</p>
<pre class="programlisting">
/pub/NetBSD/packages/
distfiles/
# Unpacked pkgsrc trees
pkgsrc-current -> /pub/NetBSD/NetBSD-current/pkgsrc
pkgsrc-2003Q4 -> N/A
pkgsrc-2004Q1/pkgsrc
# pkgsrc archives
pkgsrc-current.tar.gz -> ../NetBSD-current/tar_files/pkgsrc.tar.gz
pkgsrc-2003Q4.tar.gz -> N/A
pkgsrc-2004Q1.tar.gz -> N/A
# Per pkgsrc-release/OS-release/arch package archives
pkgsrc-2003Q4/
NetBSD-1.6.2/
i386/
All/
archivers/
foo -> ../All/foo
...
pkgsrc-2004Q1/
NetBSD-1.6.2/
i386/
All/
...
NetBSD-2.0/
i386/
All/
...
SunOS-5.9/
sparc/
All/
...
x86/
All/
...
# Per os-release package archive convenience links
NetBSD-1.6.2 -> 1.6.2
1.6.2/
i386 -> ../pkgsrc-2004Q1/NetBSD-1.6.2/i386
m68k/
All/
archivers/
foo -> ../All/foo
...
amiga -> m68k
atari -> m68k
...
2.0 -> NetBSD-2.0 # backward compat, historic
NetBSD-2.0/
i386 -> ../pkgsrc-2004Q1/NetBSD-2.0/i386
SunOS-5.9/
sparc -> ../pkgsrc-2004Q1/SunOS-5.9/sparc
x86 -> ../pkgsrc-2004Q1/SunOS-5.9/x86
</pre>
<p>To create:</p>
<div class="orderedlist">
<ol type="1">
<li>
<p>Run bulk build, see <a href="#bulkbuild" title=
"5.3. Doing a bulk build of all packages">Section
5.3, “Doing a bulk build of all
packages”</a></p>
</li>
<li>
<p>Upload /usr/pkgsrc/packages to</p>
<pre class="programlisting">
ftp://ftp.NetBSD.org/pub/NetBSD/packages/\
pkgsrc-2004Q4/\ # pkgsrc-branch
`uname -s`-`uname -r`/ # OS & version
`uname -p` # architecture
</pre>
</li>
<li>
<p>If necessary, create a symlink <span><strong class=
"command">ln -s `uname -m` `uname -p`</strong></span>
(amiga -> m68k, ...)</p>
</li>
</ol>
</div>
</div>
<div class="appendix" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a name="editing" id=
"editing"></a>Appendix D. Editing guidelines
for the pkgsrc guide</h2>
</div>
</div>
</div>
<div class="toc">
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="sect1"><a href="#targets">D.1.
Targets</a></span></dt>
<dt><span class="sect1"><a href="#procedure">D.2.
Procedure</a></span></dt>
</dl>
</div>
<p>This section contains information on editing the pkgsrc
guide itself.</p>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"targets" id="targets"></a>D.1. Targets</h2>
</div>
</div>
</div>
<p>The pkgsrc guide's source code is stored in <code class=
"filename">pkgsrc/doc/guide/files</code>, and several files
are created from it:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p><code class=
"filename">pkgsrc/doc/pkgsrc.txt</code></p>
</li>
<li>
<p><code class=
"filename">pkgsrc/doc/pkgsrc.html</code></p>
</li>
<li>
<p><code class=
"filename">http://www.NetBSD.org/Documentation/pkgsrc/</code>:
the documentation on the NetBSD website will be built
from pkgsrc and kept up to date on the web server
itself. This means you <span class=
"emphasis"><em>must</em></span> make sure that your
changes haven't broken the build!</p>
</li>
<li>
<p><code class=
"filename">http://www.NetBSD.org/Documentation/pkgsrc/pkgsrc.pdf</code>:
PDF version of the pkgsrc guide.</p>
</li>
<li>
<p><code class=
"filename">http://www.NetBSD.org/Documentation/pkgsrc/pkgsrc.ps</code>:
PostScript version of the pkgsrc guide.</p>
</li>
</ul>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name=
"procedure" id=
"procedure"></a>D.2. Procedure</h2>
</div>
</div>
</div>
<p>The procedure to edit the pkgsrc guide is:</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>Make sure you have the packages needed to
re-generate the pkgsrc guide (and other XML-based
NetBSD documentation) installed. These are
“<span class="quote">netbsd-doc</span>”
for creating the ASCII- and HTML-version, and
“<span class=
"quote">netbsd-doc-print</span>”for the
PostScript- and PDF version. You will need both
packages installed, to make sure documentation is
consistent across all formats. The packages can be
found in <code class=
"filename">pkgsrc/meta-pkgs/netbsd-doc</code> and
<code class=
"filename">pkgsrc/meta-pkgs/netbsd-doc-print</code>.</p>
</li>
<li>
<p>Edit the XML file(s) in <code class=
"filename">pkgsrc/doc/guide/files</code>.</p>
</li>
<li>
<p>Run <span><strong class="command">make extract
&& make do-lint</strong></span> in
<code class="filename">pkgsrc/doc/guide</code> to
check the XML syntax, and fix it if needed.</p>
</li>
<li>
<p>Run <span><strong class=
"command">make</strong></span> in <code class=
"filename">pkgsrc/doc/guide</code> to build the HTML
and ASCII version.</p>
</li>
<li>
<p>If all is well, run <span><strong class=
"command">make install-doc</strong></span> to put the
generated files into <code class=
"filename">pkgsrc/doc</code>.</p>
</li>
<li>
<p><span><strong class="command">cvs commit
pkgsrc/doc/guide/files</strong></span></p>
</li>
<li>
<p><span><strong class="command">cvs commit -m
re-generate
pkgsrc/doc/pkgsrc.{html,txt}</strong></span></p>
</li>
<li>
<p>Until the webserver on www.NetBSD.org is really
updated automatically to pick up changes to the
pkgsrc guide automatically, also run
<span><strong class="command">make install-htdocs
HTDOCSDIR=../../../htdocs</strong></span> (or
similar, adjust <code class=
"varname">HTDOCSDIR</code>!).</p>
</li>
<li>
<p><span><strong class="command">cvs commit
htdocs/Documentation/pkgsrc</strong></span></p>
</li>
</ul>
</div>
</div>
</div>
</div>
</body>
</html>
|
