| @@ -1,14 +1,14 @@ | | | @@ -1,14 +1,14 @@ |
1 | $NetBSD: README,v 1.17 2020/04/23 19:02:20 gdt Exp $ | | 1 | $NetBSD: README,v 1.18 2020/04/24 16:19:06 nia Exp $ |
2 | | | 2 | |
3 | To try to get pkgsrc working on your system, please try the following | | 3 | To try to get pkgsrc working on your system, please try the following |
4 | as root: | | 4 | as root: |
5 | | | 5 | |
6 | # ./bootstrap | | 6 | # ./bootstrap |
7 | [ --workdir <workdir> ] | | 7 | [ --workdir <workdir> ] |
8 | [ --prefix <prefix> ] | | 8 | [ --prefix <prefix> ] |
9 | [ --pkgdbdir <pkgdbdir> ] | | 9 | [ --pkgdbdir <pkgdbdir> ] |
10 | [ --sysconfdir <sysconfdir> ] | | 10 | [ --sysconfdir <sysconfdir> ] |
11 | [ --varbase <varbase> ] | | 11 | [ --varbase <varbase> ] |
12 | [ --ignore-case-check ] | | 12 | [ --ignore-case-check ] |
13 | [ --ignore-user-check ] | | 13 | [ --ignore-user-check ] |
14 | [ --preserve-path ] | | 14 | [ --preserve-path ] |
| @@ -57,27 +57,27 @@ value). If the default mk.conf doesn't a | | | @@ -57,27 +57,27 @@ value). If the default mk.conf doesn't a |
57 | copied into place. | | 57 | copied into place. |
58 | | | 58 | |
59 | | | 59 | |
60 | PER PLATFORM INFORMATION | | 60 | PER PLATFORM INFORMATION |
61 | ======================== | | 61 | ======================== |
62 | | | 62 | |
63 | pkgsrc supports or has supported many operating systems (platforms). | | 63 | pkgsrc supports or has supported many operating systems (platforms). |
64 | In general, there is a README.os for each platform that can run | | 64 | In general, there is a README.os for each platform that can run |
65 | pkgsrc, explaining particular considerations. | | 65 | pkgsrc, explaining particular considerations. |
66 | | | 66 | |
67 | Because pgksrc contains many per-platform fixes and accommodations, | | 67 | Because pgksrc contains many per-platform fixes and accommodations, |
68 | and because the presence of those at times causes more work for | | 68 | and because the presence of those at times causes more work for |
69 | others, we list platforms according to whether they are in active use. | | 69 | others, we list platforms according to whether they are in active use. |
70 | t(If you feel a platform is miscategorized, send rationale to | | 70 | (If you feel a platform is miscategorized, send rationale to |
71 | pkgsrc-users@. Include a README.platform with instructions if it is | | 71 | pkgsrc-users@. Include a README.platform with instructions if it is |
72 | missing and you are asserting that there are users. Developers should | | 72 | missing and you are asserting that there are users. Developers should |
73 | of course feel free to make improvements.) | | 73 | of course feel free to make improvements.) |
74 | | | 74 | |
75 | Note that listing a platform as having no users is not a decision to | | 75 | Note that listing a platform as having no users is not a decision to |
76 | remove it from pkgsrc; this is merely recording information that | | 76 | remove it from pkgsrc; this is merely recording information that |
77 | individual developers can use when deciding how much work is justified | | 77 | individual developers can use when deciding how much work is justified |
78 | for keeping any particular accommodation. (As always, any large-scale | | 78 | for keeping any particular accommodation. (As always, any large-scale |
79 | removals require a proposal and discussion on pkgsrc-users@.) | | 79 | removals require a proposal and discussion on pkgsrc-users@.) |
80 | | | 80 | |
81 | Note also that pkgsrc policy is that fixes to packages, unless the | | 81 | Note also that pkgsrc policy is that fixes to packages, unless the |
82 | fixes are to adjust a package to pkgsrc norms, should be filed | | 82 | fixes are to adjust a package to pkgsrc norms, should be filed |
83 | upstream and the upstream tracker URL included in the patch file or | | 83 | upstream and the upstream tracker URL included in the patch file or |