Added Debian CVS build scripts. To build a snapshot Debian release,
simply run, from within the top level of the gtk+ directory:
[ben@gilgamesh:~/src/gtk-snap/gtk+]% debian/build 1:16PM
This will build a Debian snapshot release, updating debian/changelog, and
place the resultant .debs in .. (~/src/gtk-snap/ in this example).
The version numbers are automatically updated, and look like:
YYYYMMDD.XX
where YYYY is the four-digit year (Y10K problem!) and MM is the
month (01-12) and DD is the day (01-31). XX is the build number;
it starts at 01 and debian/build increments it if you build from
CVS more than once in a day. If you're doing more than 99 CVS
builds in one day you need your head checked.
*NOTE*! The debian/build script I've written does not check in the
changes it has made to debian/changelog; that'd be scary and probably
generate too many log files all the time.
This really doesn't matter *too* much, since debian/changelog is
kind of irrelevant with CVS builds. Just know that the scant
information that is in there will not be updated via CVS.
Also, for obvious reasons, the debian/build script I've written
disables PGP signing of the resultant .changes and .dsc file.
Since these packages are not going into any archives, this will
not be a problem.
Of course, all this doesn't mean much to you if you don't have the
Debian dpkg-dev tools and debhelper installed, so don't worry if
you have no idea what I'm talking about. :)
1998-11-17 21:19:25 +00:00
|
|
|
Source: gtk+-cvs
|
|
|
|
|
Priority: extra
|
1998-03-24 04:02:49 +00:00
|
|
|
Section: libs
|
|
|
|
|
Maintainer: Ben Gertzfield <che@debian.org>
|
|
|
|
|
Standards-Version: 2.4.0.0
|
|
|
|
|
|
Added Debian CVS build scripts. To build a snapshot Debian release,
simply run, from within the top level of the gtk+ directory:
[ben@gilgamesh:~/src/gtk-snap/gtk+]% debian/build 1:16PM
This will build a Debian snapshot release, updating debian/changelog, and
place the resultant .debs in .. (~/src/gtk-snap/ in this example).
The version numbers are automatically updated, and look like:
YYYYMMDD.XX
where YYYY is the four-digit year (Y10K problem!) and MM is the
month (01-12) and DD is the day (01-31). XX is the build number;
it starts at 01 and debian/build increments it if you build from
CVS more than once in a day. If you're doing more than 99 CVS
builds in one day you need your head checked.
*NOTE*! The debian/build script I've written does not check in the
changes it has made to debian/changelog; that'd be scary and probably
generate too many log files all the time.
This really doesn't matter *too* much, since debian/changelog is
kind of irrelevant with CVS builds. Just know that the scant
information that is in there will not be updated via CVS.
Also, for obvious reasons, the debian/build script I've written
disables PGP signing of the resultant .changes and .dsc file.
Since these packages are not going into any archives, this will
not be a problem.
Of course, all this doesn't mean much to you if you don't have the
Debian dpkg-dev tools and debhelper installed, so don't worry if
you have no idea what I'm talking about. :)
1998-11-17 21:19:25 +00:00
|
|
|
Package: libgtk-cvs-1.1
|
1998-03-24 04:02:49 +00:00
|
|
|
Architecture: any
|
|
|
|
|
Section: libs
|
|
|
|
|
Depends: ${shlibs:Depends}
|
Added Debian CVS build scripts. To build a snapshot Debian release,
simply run, from within the top level of the gtk+ directory:
[ben@gilgamesh:~/src/gtk-snap/gtk+]% debian/build 1:16PM
This will build a Debian snapshot release, updating debian/changelog, and
place the resultant .debs in .. (~/src/gtk-snap/ in this example).
The version numbers are automatically updated, and look like:
YYYYMMDD.XX
where YYYY is the four-digit year (Y10K problem!) and MM is the
month (01-12) and DD is the day (01-31). XX is the build number;
it starts at 01 and debian/build increments it if you build from
CVS more than once in a day. If you're doing more than 99 CVS
builds in one day you need your head checked.
*NOTE*! The debian/build script I've written does not check in the
changes it has made to debian/changelog; that'd be scary and probably
generate too many log files all the time.
This really doesn't matter *too* much, since debian/changelog is
kind of irrelevant with CVS builds. Just know that the scant
information that is in there will not be updated via CVS.
Also, for obvious reasons, the debian/build script I've written
disables PGP signing of the resultant .changes and .dsc file.
Since these packages are not going into any archives, this will
not be a problem.
Of course, all this doesn't mean much to you if you don't have the
Debian dpkg-dev tools and debhelper installed, so don't worry if
you have no idea what I'm talking about. :)
1998-11-17 21:19:25 +00:00
|
|
|
Conflicts: libgtk-dev (<< 1:1.0.2), libgtk1.1
|
|
|
|
|
Description: CVS build of the GIMP Toolkit set of widgets for X
|
|
|
|
|
**THIS IS NOT AN OFFICIAL DEBIAN PACKAGE! THIS IS AN AUTOMATED CVS
|
|
|
|
|
BUILD OF THE GTK+ LIBRARIES! BEWARE! IT MAY NOT WORK!**
|
|
|
|
|
.
|
1998-03-24 04:02:49 +00:00
|
|
|
The GIMP Toolkit is a freely available set of widgets for X.
|
|
|
|
|
GTK is easy to use, and has been implemented in such projects as
|
|
|
|
|
The GNU Image Manipulation Program (The GIMP), GNOME, a GNU
|
|
|
|
|
desktop set of utilities for X, and gzilla, a GNU web-browser.
|
Added Debian CVS build scripts. To build a snapshot Debian release,
simply run, from within the top level of the gtk+ directory:
[ben@gilgamesh:~/src/gtk-snap/gtk+]% debian/build 1:16PM
This will build a Debian snapshot release, updating debian/changelog, and
place the resultant .debs in .. (~/src/gtk-snap/ in this example).
The version numbers are automatically updated, and look like:
YYYYMMDD.XX
where YYYY is the four-digit year (Y10K problem!) and MM is the
month (01-12) and DD is the day (01-31). XX is the build number;
it starts at 01 and debian/build increments it if you build from
CVS more than once in a day. If you're doing more than 99 CVS
builds in one day you need your head checked.
*NOTE*! The debian/build script I've written does not check in the
changes it has made to debian/changelog; that'd be scary and probably
generate too many log files all the time.
This really doesn't matter *too* much, since debian/changelog is
kind of irrelevant with CVS builds. Just know that the scant
information that is in there will not be updated via CVS.
Also, for obvious reasons, the debian/build script I've written
disables PGP signing of the resultant .changes and .dsc file.
Since these packages are not going into any archives, this will
not be a problem.
Of course, all this doesn't mean much to you if you don't have the
Debian dpkg-dev tools and debhelper installed, so don't worry if
you have no idea what I'm talking about. :)
1998-11-17 21:19:25 +00:00
|
|
|
.
|
|
|
|
|
This is the unstable 1.1 branch of GTK. It is not intended for use
|
|
|
|
|
with stable projects!
|
1998-03-24 04:02:49 +00:00
|
|
|
|
Added Debian CVS build scripts. To build a snapshot Debian release,
simply run, from within the top level of the gtk+ directory:
[ben@gilgamesh:~/src/gtk-snap/gtk+]% debian/build 1:16PM
This will build a Debian snapshot release, updating debian/changelog, and
place the resultant .debs in .. (~/src/gtk-snap/ in this example).
The version numbers are automatically updated, and look like:
YYYYMMDD.XX
where YYYY is the four-digit year (Y10K problem!) and MM is the
month (01-12) and DD is the day (01-31). XX is the build number;
it starts at 01 and debian/build increments it if you build from
CVS more than once in a day. If you're doing more than 99 CVS
builds in one day you need your head checked.
*NOTE*! The debian/build script I've written does not check in the
changes it has made to debian/changelog; that'd be scary and probably
generate too many log files all the time.
This really doesn't matter *too* much, since debian/changelog is
kind of irrelevant with CVS builds. Just know that the scant
information that is in there will not be updated via CVS.
Also, for obvious reasons, the debian/build script I've written
disables PGP signing of the resultant .changes and .dsc file.
Since these packages are not going into any archives, this will
not be a problem.
Of course, all this doesn't mean much to you if you don't have the
Debian dpkg-dev tools and debhelper installed, so don't worry if
you have no idea what I'm talking about. :)
1998-11-17 21:19:25 +00:00
|
|
|
Package: libgtk-cvs-dev
|
1998-03-24 04:02:49 +00:00
|
|
|
Architecture: any
|
|
|
|
|
Section: devel
|
Added Debian CVS build scripts. To build a snapshot Debian release,
simply run, from within the top level of the gtk+ directory:
[ben@gilgamesh:~/src/gtk-snap/gtk+]% debian/build 1:16PM
This will build a Debian snapshot release, updating debian/changelog, and
place the resultant .debs in .. (~/src/gtk-snap/ in this example).
The version numbers are automatically updated, and look like:
YYYYMMDD.XX
where YYYY is the four-digit year (Y10K problem!) and MM is the
month (01-12) and DD is the day (01-31). XX is the build number;
it starts at 01 and debian/build increments it if you build from
CVS more than once in a day. If you're doing more than 99 CVS
builds in one day you need your head checked.
*NOTE*! The debian/build script I've written does not check in the
changes it has made to debian/changelog; that'd be scary and probably
generate too many log files all the time.
This really doesn't matter *too* much, since debian/changelog is
kind of irrelevant with CVS builds. Just know that the scant
information that is in there will not be updated via CVS.
Also, for obvious reasons, the debian/build script I've written
disables PGP signing of the resultant .changes and .dsc file.
Since these packages are not going into any archives, this will
not be a problem.
Of course, all this doesn't mean much to you if you don't have the
Debian dpkg-dev tools and debhelper installed, so don't worry if
you have no idea what I'm talking about. :)
1998-11-17 21:19:25 +00:00
|
|
|
Depends: libgtk-cvs-1.1 (=${Source-Version}), libglib-cvs-dev
|
|
|
|
|
Suggests: libgtk-cvs-doc
|
|
|
|
|
Conflicts: libgtk-dev, libgtk1 (<< 1:1.0.4), libgtk1.1-dev
|
|
|
|
|
Description: CVS build of development files for the GIMP Toolkit
|
|
|
|
|
**THIS IS NOT AN OFFICIAL DEBIAN PACKAGE! THIS IS AN AUTOMATED CVS
|
|
|
|
|
BUILD OF THE GTK+ LIBRARIES! BEWARE! IT MAY NOT WORK!**
|
|
|
|
|
.
|
1998-03-24 04:02:49 +00:00
|
|
|
This package contains the header files and static libraries for the
|
|
|
|
|
GIMP Toolkit set of widgets for X.
|
|
|
|
|
.
|
Added Debian CVS build scripts. To build a snapshot Debian release,
simply run, from within the top level of the gtk+ directory:
[ben@gilgamesh:~/src/gtk-snap/gtk+]% debian/build 1:16PM
This will build a Debian snapshot release, updating debian/changelog, and
place the resultant .debs in .. (~/src/gtk-snap/ in this example).
The version numbers are automatically updated, and look like:
YYYYMMDD.XX
where YYYY is the four-digit year (Y10K problem!) and MM is the
month (01-12) and DD is the day (01-31). XX is the build number;
it starts at 01 and debian/build increments it if you build from
CVS more than once in a day. If you're doing more than 99 CVS
builds in one day you need your head checked.
*NOTE*! The debian/build script I've written does not check in the
changes it has made to debian/changelog; that'd be scary and probably
generate too many log files all the time.
This really doesn't matter *too* much, since debian/changelog is
kind of irrelevant with CVS builds. Just know that the scant
information that is in there will not be updated via CVS.
Also, for obvious reasons, the debian/build script I've written
disables PGP signing of the resultant .changes and .dsc file.
Since these packages are not going into any archives, this will
not be a problem.
Of course, all this doesn't mean much to you if you don't have the
Debian dpkg-dev tools and debhelper installed, so don't worry if
you have no idea what I'm talking about. :)
1998-11-17 21:19:25 +00:00
|
|
|
This is the unstable, 1.1 branch of GTK+. This is not intended for
|
|
|
|
|
use with stable releases of programs!
|
|
|
|
|
.
|
1998-03-24 04:02:49 +00:00
|
|
|
Install this package if you wish to develop your own X programs using
|
Added Debian CVS build scripts. To build a snapshot Debian release,
simply run, from within the top level of the gtk+ directory:
[ben@gilgamesh:~/src/gtk-snap/gtk+]% debian/build 1:16PM
This will build a Debian snapshot release, updating debian/changelog, and
place the resultant .debs in .. (~/src/gtk-snap/ in this example).
The version numbers are automatically updated, and look like:
YYYYMMDD.XX
where YYYY is the four-digit year (Y10K problem!) and MM is the
month (01-12) and DD is the day (01-31). XX is the build number;
it starts at 01 and debian/build increments it if you build from
CVS more than once in a day. If you're doing more than 99 CVS
builds in one day you need your head checked.
*NOTE*! The debian/build script I've written does not check in the
changes it has made to debian/changelog; that'd be scary and probably
generate too many log files all the time.
This really doesn't matter *too* much, since debian/changelog is
kind of irrelevant with CVS builds. Just know that the scant
information that is in there will not be updated via CVS.
Also, for obvious reasons, the debian/build script I've written
disables PGP signing of the resultant .changes and .dsc file.
Since these packages are not going into any archives, this will
not be a problem.
Of course, all this doesn't mean much to you if you don't have the
Debian dpkg-dev tools and debhelper installed, so don't worry if
you have no idea what I'm talking about. :)
1998-11-17 21:19:25 +00:00
|
|
|
the GIMP Toolkit 1.1, or if you wish to compile your own plug-ins for
|
1998-03-24 04:02:49 +00:00
|
|
|
The GIMP.
|
|
|
|
|
|
Added Debian CVS build scripts. To build a snapshot Debian release,
simply run, from within the top level of the gtk+ directory:
[ben@gilgamesh:~/src/gtk-snap/gtk+]% debian/build 1:16PM
This will build a Debian snapshot release, updating debian/changelog, and
place the resultant .debs in .. (~/src/gtk-snap/ in this example).
The version numbers are automatically updated, and look like:
YYYYMMDD.XX
where YYYY is the four-digit year (Y10K problem!) and MM is the
month (01-12) and DD is the day (01-31). XX is the build number;
it starts at 01 and debian/build increments it if you build from
CVS more than once in a day. If you're doing more than 99 CVS
builds in one day you need your head checked.
*NOTE*! The debian/build script I've written does not check in the
changes it has made to debian/changelog; that'd be scary and probably
generate too many log files all the time.
This really doesn't matter *too* much, since debian/changelog is
kind of irrelevant with CVS builds. Just know that the scant
information that is in there will not be updated via CVS.
Also, for obvious reasons, the debian/build script I've written
disables PGP signing of the resultant .changes and .dsc file.
Since these packages are not going into any archives, this will
not be a problem.
Of course, all this doesn't mean much to you if you don't have the
Debian dpkg-dev tools and debhelper installed, so don't worry if
you have no idea what I'm talking about. :)
1998-11-17 21:19:25 +00:00
|
|
|
Package: libgtk-cvs-doc
|
1998-03-24 04:02:49 +00:00
|
|
|
Architecture: all
|
Added Debian CVS build scripts. To build a snapshot Debian release,
simply run, from within the top level of the gtk+ directory:
[ben@gilgamesh:~/src/gtk-snap/gtk+]% debian/build 1:16PM
This will build a Debian snapshot release, updating debian/changelog, and
place the resultant .debs in .. (~/src/gtk-snap/ in this example).
The version numbers are automatically updated, and look like:
YYYYMMDD.XX
where YYYY is the four-digit year (Y10K problem!) and MM is the
month (01-12) and DD is the day (01-31). XX is the build number;
it starts at 01 and debian/build increments it if you build from
CVS more than once in a day. If you're doing more than 99 CVS
builds in one day you need your head checked.
*NOTE*! The debian/build script I've written does not check in the
changes it has made to debian/changelog; that'd be scary and probably
generate too many log files all the time.
This really doesn't matter *too* much, since debian/changelog is
kind of irrelevant with CVS builds. Just know that the scant
information that is in there will not be updated via CVS.
Also, for obvious reasons, the debian/build script I've written
disables PGP signing of the resultant .changes and .dsc file.
Since these packages are not going into any archives, this will
not be a problem.
Of course, all this doesn't mean much to you if you don't have the
Debian dpkg-dev tools and debhelper installed, so don't worry if
you have no idea what I'm talking about. :)
1998-11-17 21:19:25 +00:00
|
|
|
Section: doc
|
|
|
|
|
Conflicts: libgtk-dev (<< 1:0.99.4), libgtk-doc, libgtk1.1-doc
|
|
|
|
|
Description: CVS build of documentation for the GIMP Toolkit
|
|
|
|
|
**THIS IS NOT AN OFFICIAL DEBIAN PACKAGE! THIS IS AN AUTOMATED CVS
|
|
|
|
|
BUILD OF THE GTK+ LIBRARIES! BEWARE! IT MAY NOT WORK!**
|
|
|
|
|
.
|
1998-03-24 04:02:49 +00:00
|
|
|
This package contains lots of info-files, HTML docs, FAQs, and
|
|
|
|
|
other handy documentation about the GIMP Toolkit set of widgets
|
Added Debian CVS build scripts. To build a snapshot Debian release,
simply run, from within the top level of the gtk+ directory:
[ben@gilgamesh:~/src/gtk-snap/gtk+]% debian/build 1:16PM
This will build a Debian snapshot release, updating debian/changelog, and
place the resultant .debs in .. (~/src/gtk-snap/ in this example).
The version numbers are automatically updated, and look like:
YYYYMMDD.XX
where YYYY is the four-digit year (Y10K problem!) and MM is the
month (01-12) and DD is the day (01-31). XX is the build number;
it starts at 01 and debian/build increments it if you build from
CVS more than once in a day. If you're doing more than 99 CVS
builds in one day you need your head checked.
*NOTE*! The debian/build script I've written does not check in the
changes it has made to debian/changelog; that'd be scary and probably
generate too many log files all the time.
This really doesn't matter *too* much, since debian/changelog is
kind of irrelevant with CVS builds. Just know that the scant
information that is in there will not be updated via CVS.
Also, for obvious reasons, the debian/build script I've written
disables PGP signing of the resultant .changes and .dsc file.
Since these packages are not going into any archives, this will
not be a problem.
Of course, all this doesn't mean much to you if you don't have the
Debian dpkg-dev tools and debhelper installed, so don't worry if
you have no idea what I'm talking about. :)
1998-11-17 21:19:25 +00:00
|
|
|
for X.
|
1998-03-24 04:02:49 +00:00
|
|
|
.
|
Added Debian CVS build scripts. To build a snapshot Debian release,
simply run, from within the top level of the gtk+ directory:
[ben@gilgamesh:~/src/gtk-snap/gtk+]% debian/build 1:16PM
This will build a Debian snapshot release, updating debian/changelog, and
place the resultant .debs in .. (~/src/gtk-snap/ in this example).
The version numbers are automatically updated, and look like:
YYYYMMDD.XX
where YYYY is the four-digit year (Y10K problem!) and MM is the
month (01-12) and DD is the day (01-31). XX is the build number;
it starts at 01 and debian/build increments it if you build from
CVS more than once in a day. If you're doing more than 99 CVS
builds in one day you need your head checked.
*NOTE*! The debian/build script I've written does not check in the
changes it has made to debian/changelog; that'd be scary and probably
generate too many log files all the time.
This really doesn't matter *too* much, since debian/changelog is
kind of irrelevant with CVS builds. Just know that the scant
information that is in there will not be updated via CVS.
Also, for obvious reasons, the debian/build script I've written
disables PGP signing of the resultant .changes and .dsc file.
Since these packages are not going into any archives, this will
not be a problem.
Of course, all this doesn't mean much to you if you don't have the
Debian dpkg-dev tools and debhelper installed, so don't worry if
you have no idea what I'm talking about. :)
1998-11-17 21:19:25 +00:00
|
|
|
This package documents the unstable 1.1 release of the GIMP Toolkit.
|
|
|
|
|
.
|
1998-03-24 04:02:49 +00:00
|
|
|
Install this package if you want to have lots of info about the
|
|
|
|
|
GIMP toolkit when you're programming.
|
Added Debian CVS build scripts. To build a snapshot Debian release,
simply run, from within the top level of the gtk+ directory:
[ben@gilgamesh:~/src/gtk-snap/gtk+]% debian/build 1:16PM
This will build a Debian snapshot release, updating debian/changelog, and
place the resultant .debs in .. (~/src/gtk-snap/ in this example).
The version numbers are automatically updated, and look like:
YYYYMMDD.XX
where YYYY is the four-digit year (Y10K problem!) and MM is the
month (01-12) and DD is the day (01-31). XX is the build number;
it starts at 01 and debian/build increments it if you build from
CVS more than once in a day. If you're doing more than 99 CVS
builds in one day you need your head checked.
*NOTE*! The debian/build script I've written does not check in the
changes it has made to debian/changelog; that'd be scary and probably
generate too many log files all the time.
This really doesn't matter *too* much, since debian/changelog is
kind of irrelevant with CVS builds. Just know that the scant
information that is in there will not be updated via CVS.
Also, for obvious reasons, the debian/build script I've written
disables PGP signing of the resultant .changes and .dsc file.
Since these packages are not going into any archives, this will
not be a problem.
Of course, all this doesn't mean much to you if you don't have the
Debian dpkg-dev tools and debhelper installed, so don't worry if
you have no idea what I'm talking about. :)
1998-11-17 21:19:25 +00:00
|
|
|
|
|
|
|
|
Package: libgtk-cvs-dbg
|
|
|
|
|
Architecture: any
|
|
|
|
|
Section: devel
|
|
|
|
|
Depends: libgtk-cvs-1.1 (= ${Source-Version}), libgtk-cvs-dev (= ${Source-Version})
|
|
|
|
|
Suggests: libgtk-cvs-doc
|
|
|
|
|
Conflicts: libgtk1.1-dbg
|
|
|
|
|
Description: CVS build of debugging files for the GIMP Toolkit
|
|
|
|
|
**THIS IS NOT AN OFFICIAL DEBIAN PACKAGE! THIS IS AN AUTOMATED CVS
|
|
|
|
|
BUILD OF THE GTK+ LIBRARIES! BEWARE! IT MAY NOT WORK!**
|
|
|
|
|
.
|
|
|
|
|
This package contains the debugging static libraries for the
|
|
|
|
|
GIMP Toolkit set of widgets for X.
|
|
|
|
|
.
|
|
|
|
|
This is the unstable, 1.1 branch of GTK+. This is not intended for
|
|
|
|
|
use with stable releases of programs!
|
|
|
|
|
.
|
|
|
|
|
Install this package if you wish to debug your own X programs using
|
|
|
|
|
the GIMP Toolkit 1.1, or if you wish to debug your own plug-ins for
|
|
|
|
|
The GIMP.
|