pkgng

Check-in [e062ddc7c6]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Latest links are no longer generated per category for ports with pkgng
Timelines: family | ancestors | trunk | multi-repos | stash | release-1.1
Files: files | file ages | folders
SHA1: e062ddc7c6ff4c98dfb9fe7b2c5f23c302c75e6d
User & Date: bryan@shatow.net 2013-09-30 16:02:38
Context
2013-09-30
16:02
Latest links are no longer generated per category for ports with pkgng Leaf check-in: e062ddc7c6 user: bryan@shatow.net tags: trunk, multi-repos, stash, release-1.1
16:02
Spelling and typo fixes check-in: e37b0d7b23 user: bryan@shatow.net tags: trunk, multi-repos, stash, release-1.1
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to libpkg/pkg-repository.5.

142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
Contains a YAML document listing all of the files contained in all
of the packages within the repository.
.Pp
The repository may optionally contain sub-directories corresponding to
the package origins within the
.Os
ports tree.
.It Pa $REPOSITORY_ROOT/accessibility/
.It Pa $REPOSITORY_ROOT/archivers/
.It Pa ...
.It Pa $REPOSITORY_ROOT/x11-toolkits/
These are populated by per-package symbolic links to the actual
package content stored within
.Pa $REPOSITORY_ROOT/All/
according to the package origin within the FreeBSD ports collection.
Package symbolic links contain the package name and version.
.El
.Pp
Each of the packages listed in the repository catalogue must have a
unique
.Cm origin .
There are no other constraints: package sets are not required to be
either complete (i.e., with all dependencies satisfied) or







<
<
<
<
<
<
<
<
<







142
143
144
145
146
147
148









149
150
151
152
153
154
155
Contains a YAML document listing all of the files contained in all
of the packages within the repository.
.Pp
The repository may optionally contain sub-directories corresponding to
the package origins within the
.Os
ports tree.









.El
.Pp
Each of the packages listed in the repository catalogue must have a
unique
.Cm origin .
There are no other constraints: package sets are not required to be
either complete (i.e., with all dependencies satisfied) or