pkgsrc/doc/guide, branch trunk [no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk 2022-12-06T01:37:11Z fixes.xml: add more explanatory detail about GITHUB_TAG use 2022-12-06T01:37:11Z gutteridge gutteridge@pkgsrc.org 2022-12-06T01:37:11Z urn:sha1:e90d99e37c629318ac1ad42a26bf79a3233a4e06 buildlink.xml: drop RCS ID from code example 2022-12-06T00:36:13Z gutteridge gutteridge@pkgsrc.org 2022-12-06T00:36:13Z urn:sha1:3fbeaa770ce0f3b218d7d508739a85cea5e7d8ed It served no real purpose here, and causes CVS to inject the revision details of the generated HTML file on each update instead. introduction.xml: more adjustments for defunct items 2022-12-03T02:17:44Z gutteridge gutteridge@pkgsrc.org 2022-12-03T02:17:44Z urn:sha1:3f303a5490e1113689d47abaca25d99638112f6b Remove reference to README.IRIX5.3, and fix alignment of Bitrig note. introduction.xml: capitalize Bourne 2022-12-03T01:58:18Z gutteridge gutteridge@pkgsrc.org 2022-12-03T01:58:18Z urn:sha1:6271c430235f279ad5f5e4d4950483265192afe6 guide: document how to test yes/no variables 2022-11-18T19:35:03Z rillig rillig@pkgsrc.org 2022-11-18T19:35:03Z urn:sha1:a3cc4bb334bada4aeaf24fdaeacf24b086c943f1 https://mail-index.netbsd.org/tech-pkg/2022/11/16/msg026992.html fixes.xml: add a small section about atomic64.mk 2022-08-08T01:54:32Z gutteridge gutteridge@pkgsrc.org 2022-08-08T01:54:32Z urn:sha1:110f333f4bd91a1834b151de373accf745ec3f0a doc/guide: clean up conditions in package makefile 2022-07-25T05:57:18Z rillig rillig@pkgsrc.org 2022-07-25T05:57:18Z urn:sha1:d75cafc43d23c9265b545a443d7644468dbcd49d The condition 'defined(OUTPUT)' was always true. Since OUTPUT is guaranteed to defined, there is no need to use the complicated '!empty'. No functional change. doc/guide: document how PKGPATH is typically used 2022-07-25T05:42:22Z rillig rillig@pkgsrc.org 2022-07-25T05:42:22Z urn:sha1:ec3ef0214845912636e32415a16067b01eda2781 doc: remove half sentence about packages with the same PKGNAME 2022-07-23T06:45:32Z wiz wiz@pkgsrc.org 2022-07-23T06:45:32Z urn:sha1:f2d7930666c8804a1daf01e77f68f136f03e00e0 It's confusing in the context of the CONFLICTS section, since packages with the same PKGNAME conflict automatically. fixes.xml: add a comment about conflicting PKGNAME entries 2022-07-19T01:58:04Z gutteridge gutteridge@pkgsrc.org 2022-07-19T01:58:04Z urn:sha1:5c6118009838d7c1d931fe5214d7727bd58e2072 While here, fix some style.