NOTICE: This package has been removed from pkgsrc

./x11/qt1, C++ X GUI toolkit

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ]


Branch: CURRENT, Version: 1.44nb3, Package name: qt1-1.44nb3, Maintainer: pkgsrc-users

Qt(TM) is a GUI software toolkit. Qt simplifies the task of writing and
maintaining GUI (graphical user interface) applications.
Qt is written in C++ and is fully object-oriented. It has everything you need
to create professional GUI applications. And it enables you to create them
quickly.
Qt is a multi-platform toolkit. When developing software with Qt, you can run
it on the X Window System (Unix/X11) or Microsoft Windows NT and Windows 95/98.
Simply recompile your source code on the platform you want.
Qt cuts down the complexity in implementing large and complex systems. Its
ingenious signal-slot technology enables true component programming.


Required to build:
[pkgtools/xpkgwedge] [pkgtools/x11-links] [devel/gmake] [devel/libtool-base] [x11/xextproto]

Master sites: (Expand)

SHA1: 08848fe5534bb210b151a1d9f3480fe83c0053c1
RMD160: f15179396774f4038a082e984d8bdd4a7c4d1ae1
Filesize: 2597.655 KB

Version history: (Expand)


CVS history: (Expand)


   2007-01-17 04:11:19 by Roland Illig | Files touched by this commit (20)
Log message:
Renamed BUILDLINK_TRANSFORM.* to BUILDLINK_FNAME_TRANSFORM.*, to make
clear that these variables are completely unrelated to
BUILDLINK_TRANSFORM.

Added a legacy check that catches appearances of BUILDLINK_TRANSFORM.*.

XXX: Where should incompatible changes in pkgsrc be documented?
   2007-01-13 19:42:35 by Joerg Sonnenberger | Files touched by this commit (2)
Log message:
Modular Xorg support. Not linked correctly though.
   2006-10-05 00:06:57 by Thomas Klausner | Files touched by this commit (16)
Log message:
Update MASTER_SITES and/or HOMEPAGE, from Sergey Svishchev.
   2006-07-09 01:11:17 by Johnny C. Lam | Files touched by this commit (877)
Log message:
Change the format of BUILDLINK_ORDER to contain depth information as well,
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
   2006-07-09 00:39:49 by Johnny C. Lam | Files touched by this commit (877)
Log message:
Track information in a new variable BUILDLINK_ORDER that informs us
of the order in which buildlink3.mk files are (recursively) included
by a package Makefile.
   2006-04-12 12:27:47 by Roland Illig | Files touched by this commit (749)
Log message:
Aligned the last line of the buildlink3.mk files with the first line, so
that they look nicer.
   2006-04-06 08:23:06 by Jeremy C. Reed | Files touched by this commit (1147)
Log message:
Over 1200 files touched but no revisions bumped :)

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).
   2006-03-04 22:31:14 by Johnny C. Lam | Files touched by this commit (2257)
Log message:
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to \ 
"pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.