<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pkgsrc/lang/python23-nth/buildlink3.mk, branch pkgsrc_2008Q2</title>
<subtitle>[no description]</subtitle>
<id>https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2008Q2</id>
<link rel='self' href='https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2008Q2'/>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/'/>
<updated>2006-07-08T23:10:35Z</updated>
<entry>
<title>Change the format of BUILDLINK_ORDER to contain depth information as well,</title>
<updated>2006-07-08T23:10:35Z</updated>
<author>
<name>jlam</name>
<email>jlam</email>
</author>
<published>2006-07-08T23:10:35Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=b96729a13e6502c6d9d1c2912a698e23f57d3965'/>
<id>urn:sha1:b96729a13e6502c6d9d1c2912a698e23f57d3965</id>
<content type='text'>
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.

For example, "make show-buildlink3" in fonts/Xft2 displays:

	zlib
	fontconfig
	    iconv
	    zlib
	    freetype2
	    expat
	freetype2
	Xrender
	    renderproto
</content>
</entry>
<entry>
<title>Track information in a new variable BUILDLINK_ORDER that informs us</title>
<updated>2006-07-08T22:38:58Z</updated>
<author>
<name>jlam</name>
<email>jlam</email>
</author>
<published>2006-07-08T22:38:58Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=6e7d67f4b1fea88b6cff1f00142907eca4188add'/>
<id>urn:sha1:6e7d67f4b1fea88b6cff1f00142907eca4188add</id>
<content type='text'>
of the order in which buildlink3.mk files are (recursively) included
by a package Makefile.
</content>
</entry>
<entry>
<title>Aligned the last line of the buildlink3.mk files with the first line, so</title>
<updated>2006-04-12T10:26:59Z</updated>
<author>
<name>rillig</name>
<email>rillig</email>
</author>
<published>2006-04-12T10:26:59Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=f39c7a6814118271c6fbfe87140ce12d8a3146d7'/>
<id>urn:sha1:f39c7a6814118271c6fbfe87140ce12d8a3146d7</id>
<content type='text'>
that they look nicer.
</content>
</entry>
<entry>
<title>Over 1200 files touched but no revisions bumped :)</title>
<updated>2006-04-06T06:21:32Z</updated>
<author>
<name>reed</name>
<email>reed</email>
</author>
<published>2006-04-06T06:21:32Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=3b50716541c42bd031d14157665a74004901cade'/>
<id>urn:sha1:3b50716541c42bd031d14157665a74004901cade</id>
<content type='text'>
RECOMMENDED is removed. It becomes ABI_DEPENDS.

BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.

BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.

BUILDLINK_DEPENDS does not change.

IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".

Added to obsolete.mk checking for IGNORE_RECOMMENDED.

I did not manually go through and fix any aesthetic tab/spacing issues.

I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.

I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.

As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.

As discussed on tech-pkg.

I will commit to revbump, pkglint, pkg_install, createbuildlink separately.

Note that if you use wip, it will fail!  I will commit to pkgsrc-wip
later (within day).
</content>
</entry>
<entry>
<title>Recursive revision bump / recommended bump for gettext ABI change.</title>
<updated>2006-02-05T23:08:03Z</updated>
<author>
<name>joerg</name>
<email>joerg</email>
</author>
<published>2006-02-05T23:08:03Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=93e3b9e04264b93620166058e19ea42c856505b0'/>
<id>urn:sha1:93e3b9e04264b93620166058e19ea42c856505b0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix typo (BUILDLINK_DENTH -&gt; BUILDLINK_DEPTH).</title>
<updated>2005-01-28T22:28:44Z</updated>
<author>
<name>hira</name>
<email>hira</email>
</author>
<published>2005-01-28T22:28:44Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=d7fcacf23c301e03c9f0f0c03ac091be297242d4'/>
<id>urn:sha1:d7fcacf23c301e03c9f0f0c03ac091be297242d4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Intial import of Python 2.3.4 / without thread</title>
<updated>2005-01-23T22:57:19Z</updated>
<author>
<name>recht</name>
<email>recht</email>
</author>
<published>2005-01-23T22:57:19Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=245b543755e935b586aba7ceb903ab0358486870'/>
<id>urn:sha1:245b543755e935b586aba7ceb903ab0358486870</id>
<content type='text'>
support (what used to be the python23 package).

Python is an interpreted, interactive, object-oriented
programming language that combines remarkable power with
very clear syntax. For an introduction to programming in
Python you are referred to the Python Tutorial. The
Python Library Reference documents built-in and standard
types, constants, functions and modules. Finally, the
Python Reference Manual describes the syntax and semantics
of the core language in (perhaps too) much detail.

Python's basic power can be extended with your own modules
written in C or C++. On most systems such modules may be
dynamically loaded. Python is also adaptable as an exten-
sion language for existing applications. See the internal
documentation for hints.

This package has been compiled without support for threads.
</content>
</entry>
</feed>
