1998-03-24 04:02:49 +00:00
|
|
|
#!/usr/bin/make -f
|
|
|
|
|
|
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
|
|
|
# debian/rules file for gtk+ Debian package
|
|
|
|
|
# written April 1998 by Ben Gertzfield <che@debian.org
|
1998-03-24 04:02:49 +00:00
|
|
|
|
|
|
|
|
build: build-stamp
|
|
|
|
|
build-stamp:
|
|
|
|
|
dh_testdir
|
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
|
|
|
./autogen.sh --prefix=/usr --with-xinput=xfree
|
1998-03-24 04:02:49 +00:00
|
|
|
$(MAKE)
|
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
|
|
|
cd docs && make distdocs
|
1998-03-24 04:02:49 +00:00
|
|
|
cd ..
|
|
|
|
|
touch build-stamp
|
|
|
|
|
|
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
|
|
|
build-dbg: build-dbg-stamp
|
|
|
|
|
build-dbg-stamp:
|
|
|
|
|
dh_testdir
|
|
|
|
|
./configure --prefix=/usr --with-xinput=xfree --enable-debug=yes
|
|
|
|
|
$(MAKE)
|
|
|
|
|
touch build-dbg-stamp
|
|
|
|
|
|
1998-03-24 04:02:49 +00:00
|
|
|
clean:
|
|
|
|
|
dh_testdir
|
|
|
|
|
dh_testroot
|
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
|
|
|
rm -f build-stamp build-dbg-stamp install-stamp install-dbg-stamp
|
1998-03-24 04:02:49 +00:00
|
|
|
# Add here commands to clean up after the build process.
|
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
|
|
|
-$(MAKE) clean
|
|
|
|
|
cd docs
|
|
|
|
|
-$(MAKE) maintainer-clean
|
|
|
|
|
cd ..
|
1998-03-24 04:02:49 +00:00
|
|
|
-$(MAKE) distclean
|
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
|
|
|
find . -name '*.o' -o -name '_libs' -o -name '*.lo' -o -name '*.a' -o -name '.deps' | xargs rm -rf
|
1998-03-24 04:02:49 +00:00
|
|
|
dh_clean
|
|
|
|
|
|
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
|
|
|
clean-dbg:
|
|
|
|
|
dh_testdir
|
|
|
|
|
dh_testroot
|
|
|
|
|
rm -f build-stamp build-dbg-stamp install-stamp install-dbg-stamp
|
|
|
|
|
# Add here commands to clean up after the build process.
|
|
|
|
|
-$(MAKE) clean
|
|
|
|
|
cd docs
|
|
|
|
|
-$(MAKE) maintainer-clean
|
|
|
|
|
cd ..
|
|
|
|
|
-$(MAKE) distclean
|
|
|
|
|
find . -name '*.o' -o -name '_libs' -o -name '*.lo' -o -name '*.a' -o -name '.deps' | xargs rm -rf
|
|
|
|
|
dh_clean -k
|
|
|
|
|
|
1998-03-24 04:02:49 +00:00
|
|
|
install: install-stamp
|
|
|
|
|
install-stamp: build
|
|
|
|
|
dh_testdir
|
|
|
|
|
dh_testroot
|
|
|
|
|
dh_clean
|
|
|
|
|
$(MAKE) prefix=`pwd`/debian/tmp/usr install
|
|
|
|
|
touch install-stamp
|
|
|
|
|
|
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
|
|
|
install-dbg: install-dbg-stamp
|
|
|
|
|
install-dbg-stamp: build-dbg
|
|
|
|
|
dh_testdir
|
|
|
|
|
dh_testroot
|
|
|
|
|
dh_clean -k
|
|
|
|
|
$(MAKE) prefix=`pwd`/debian/libgtk-cvs-dbg/usr install
|
|
|
|
|
touch install-dbg-stamp
|
|
|
|
|
|
1998-03-24 04:02:49 +00:00
|
|
|
# Build architecture-independent files here.
|
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
|
|
|
binary-indep: build install libgtk-cvs-doc
|
1998-03-24 04:02:49 +00:00
|
|
|
# We have nothing to do by default.
|
|
|
|
|
|
|
|
|
|
# Build architecture-dependent files here.
|
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
|
|
|
binary-arch: build install libgtk-cvs-dev libgtk-cvs-1.1 libgtk-cvs-dbg
|
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
|
|
|
libgtk-cvs-1.1: build
|
|
|
|
|
dh_testdir -plibgtk-cvs-1.1
|
|
|
|
|
dh_testroot -plibgtk-cvs-1.1
|
|
|
|
|
dh_installdirs -plibgtk-cvs-1.1
|
1998-03-24 04:02:49 +00:00
|
|
|
# Add here commands to install the files into debian/tmp
|
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
|
|
|
rm -rf debian/tmp/usr/bin debian/tmp/usr/include debian/tmp/usr/info debian/tmp/usr/lib/glib debian/tmp/usr/share/aclocal debian/tmp/usr/man debian/tmp/usr/lib/*.la
|
|
|
|
|
dh_installdocs -plibgtk-cvs-1.1
|
|
|
|
|
dh_installchangelogs -plibgtk-cvs-1.1
|
|
|
|
|
dh_strip -plibgtk-cvs-1.1
|
|
|
|
|
dh_compress -plibgtk-cvs-1.1
|
|
|
|
|
dh_fixperms -plibgtk-cvs-1.1
|
|
|
|
|
dh_installdeb -plibgtk-cvs-1.1
|
|
|
|
|
dh_shlibdeps -plibgtk-cvs-1.1
|
|
|
|
|
dh_gencontrol -plibgtk-cvs-1.1
|
1998-11-18 06:25:35 +00:00
|
|
|
dh_makeshlibs -plibgtk-cvs-1.1 -V 'libgtk-cvs-1.1 (='`cat debian/version`')'
|
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
|
|
|
dh_md5sums -plibgtk-cvs-1.1
|
|
|
|
|
dh_builddeb -plibgtk-cvs-1.1
|
|
|
|
|
|
|
|
|
|
libgtk-cvs-dev: build
|
|
|
|
|
dh_testdir -plibgtk-cvs-dev
|
|
|
|
|
dh_testroot -plibgtk-cvs-dev
|
|
|
|
|
dh_clean -plibgtk-cvs-dev -k
|
|
|
|
|
dh_installdirs -plibgtk-cvs-dev
|
1998-03-24 04:02:49 +00:00
|
|
|
# Add here commands to install the files into debian/tmp
|
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
|
|
|
dh_movefiles -plibgtk-cvs-dev
|
1998-03-24 04:02:49 +00:00
|
|
|
cp gtk-config debian/tmp/usr/bin
|
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
|
|
|
dh_installdocs -plibgtk-cvs-dev
|
|
|
|
|
dh_installchangelogs -plibgtk-cvs-dev
|
|
|
|
|
dh_strip -plibgtk-cvs-dev
|
|
|
|
|
dh_compress -plibgtk-cvs-dev
|
|
|
|
|
dh_fixperms -plibgtk-cvs-dev
|
|
|
|
|
dh_installdeb -plibgtk-cvs-dev
|
|
|
|
|
dh_shlibdeps -plibgtk-cvs-dev
|
|
|
|
|
dh_gencontrol -plibgtk-cvs-dev
|
|
|
|
|
dh_md5sums -plibgtk-cvs-dev
|
|
|
|
|
dh_builddeb -plibgtk-cvs-dev
|
|
|
|
|
|
|
|
|
|
libgtk-cvs-doc:
|
|
|
|
|
dh_testdir -plibgtk-cvs-doc
|
|
|
|
|
dh_testroot -plibgtk-cvs-doc
|
|
|
|
|
dh_clean -plibgtk-cvs-doc -k
|
|
|
|
|
dh_installdirs -plibgtk-cvs-doc usr/doc/libgtk-cvs-doc/faq-html \
|
|
|
|
|
usr/doc/libgtk-cvs-doc/tutorial-html usr/doc/libgtk-cvs-doc/italian-tutorial-html usr/doc/libgtk-cvs-doc/french-tutorial-html usr/doc/libgtk-cvs-doc/gdk-html
|
|
|
|
|
dh_movefiles -plibgtk-cvs-doc
|
|
|
|
|
cp docs/html/gtkfaq*.html debian/libgtk-cvs-doc/usr/doc/libgtk-cvs-doc/faq-html
|
|
|
|
|
cp docs/html/gtk_tut-*.html debian/libgtk-cvs-doc/usr/doc/libgtk-cvs-doc/tutorial-html
|
|
|
|
|
cp docs/html/*.gif debian/libgtk-cvs-doc/usr/doc/libgtk-cvs-doc/tutorial-html
|
|
|
|
|
cp docs/html/gtk_tut.html debian/libgtk-cvs-doc/usr/doc/libgtk-cvs-doc/tutorial-html
|
|
|
|
|
cp docs/html/gtk_tut_it*.html debian/libgtk-cvs-doc/usr/doc/libgtk-cvs-doc/italian-tutorial-html
|
|
|
|
|
cp docs/html/*.gif debian/libgtk-cvs-doc/usr/doc/libgtk-cvs-doc/italian-tutorial-html
|
|
|
|
|
cp docs/html/gtk_tut_fr*.html debian/libgtk-cvs-doc/usr/doc/libgtk-cvs-doc/french-tutorial-html
|
|
|
|
|
cp docs/html/*.gif debian/libgtk-cvs-doc/usr/doc/libgtk-cvs-doc/french-tutorial-html
|
|
|
|
|
cp docs/html/gdk* debian/libgtk-cvs-doc/usr/doc/libgtk-cvs-doc/gdk-html
|
|
|
|
|
cp docs/text/*.txt debian/libgtk-cvs-doc/usr/doc/libgtk-cvs-doc/
|
|
|
|
|
|
|
|
|
|
dh_installdocs -plibgtk-cvs-doc docs/{debugging,developers,styles,text_widget,widget_system,gtk-config,refcounting}.txt TODO NEWS
|
|
|
|
|
dh_installchangelogs -plibgtk-cvs-doc
|
|
|
|
|
dh_strip -plibgtk-cvs-doc
|
|
|
|
|
dh_compress -plibgtk-cvs-doc
|
|
|
|
|
dh_fixperms -plibgtk-cvs-doc
|
|
|
|
|
dh_installdeb -plibgtk-cvs-doc
|
|
|
|
|
dh_shlibdeps -plibgtk-cvs-doc
|
|
|
|
|
dh_gencontrol -plibgtk-cvs-doc
|
|
|
|
|
dh_md5sums -plibgtk-cvs-doc
|
|
|
|
|
dh_builddeb -plibgtk-cvs-doc
|
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
|
|
|
libgtk-cvs-dbg: clean-dbg install-dbg
|
|
|
|
|
dh_testdir -plibgtk-cvs-dbg
|
|
|
|
|
dh_testroot -plibgtk-cvs-dbg
|
|
|
|
|
dh_installdirs -plibgtk-cvs-dbg
|
|
|
|
|
# Add here commands to install the files into debian/libgtk-cvs-dbg
|
|
|
|
|
rm -rf debian/libgtk-cvs-dbg/usr/bin debian/libgtk-cvs-dbg/usr/include debian/libgtk-cvs-dbg/usr/info debian/libgtk-cvs-dbg/usr/lib/glib debian/libgtk-cvs-dbg/usr/man debian/libgtk-cvs-dbg/usr/share debian/libgtk-cvs-dbg/usr/lib/*.{la,so*}
|
|
|
|
|
for file in `find debian/libgtk-cvs-dbg/usr/lib -name '*.a'` ; do \
|
|
|
|
|
mv $$file debian/libgtk-cvs-dbg/usr/lib/`basename $$file .a`_g.a; \
|
|
|
|
|
done
|
|
|
|
|
dh_installdocs -plibgtk-cvs-dbg
|
|
|
|
|
dh_installchangelogs -plibgtk-cvs-dbg
|
|
|
|
|
dh_compress -plibgtk-cvs-dbg
|
|
|
|
|
dh_fixperms -plibgtk-cvs-dbg
|
|
|
|
|
dh_installdeb -plibgtk-cvs-dbg
|
|
|
|
|
dh_shlibdeps -plibgtk-cvs-dbg
|
|
|
|
|
dh_gencontrol -plibgtk-cvs-dbg
|
|
|
|
|
dh_md5sums -plibgtk-cvs-dbg
|
|
|
|
|
dh_builddeb -plibgtk-cvs-dbg
|
1998-03-24 04:02:49 +00:00
|
|
|
|
|
|
|
|
source diff:
|
|
|
|
|
@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
|
|
|
|
|
|
|
|
|
|
binary: binary-indep binary-arch
|
|
|
|
|
.PHONY: build clean binary-indep binary-arch binary
|