Subversion Repositories liboop

Compare Revisions

Ignore whitespace Rev 41 → Rev 40

/tags/1.0-8/debian/source/format
File deleted
/tags/1.0-8/debian/control
File deleted
/tags/1.0-8/debian/liboop-doc.doc-base
File deleted
/tags/1.0-8/debian/compat
File deleted
/tags/1.0-8/debian/liboop-dev.install
File deleted
/tags/1.0-8/debian/watch
File deleted
/tags/1.0-8/debian/changelog
File deleted
/tags/1.0-8/debian/patches/configure_support_freebsd_hurd.patch
File deleted
/tags/1.0-8/debian/patches/series
File deleted
/tags/1.0-8/debian/patches/explicit_linking.patch
File deleted
/tags/1.0-8/debian/patches/read_bugfixes.patch
File deleted
/tags/1.0-8/debian/copyright
File deleted
/tags/1.0-8/debian/rules
File deleted
Property changes:
Deleted: svn:executable
## -1 +0,0 ##
-*
\ No newline at end of property
Index: 1.0-8/debian/liboop4.install
===================================================================
--- 1.0-8/debian/liboop4.install (revision 41)
+++ 1.0-8/debian/liboop4.install (nonexistent)
@@ -1 +0,0 @@
-usr/lib/lib*.so.*
Index: 1.0-8/debian/README.Debian
===================================================================
--- 1.0-8/debian/README.Debian (revision 41)
+++ 1.0-8/debian/README.Debian (nonexistent)
@@ -1,28 +0,0 @@
-liboop for Debian
------------------
-
-I've chosen at this stage not to package the adapter libraries separately,
-since the package only weighs in at just over 500k when unpacked. If anyone
-would rather that these were all in separate packages, please let me know
-and I'll think again about doing this ... At the moment, the package _DOES
-NOT DEPEND_ on any of the libraries required to use the adapter libraries,
-so if your package uses one of the adapter libraries, you _must_ depend on
-the appropriate library (ie. if you link with liboop-tcl, you must also
-depend on tcl8.3 ...). The same goes for Build-Depends.
-
-My reasoning for packaging liboop in this way is to avoid having to install
-excessive numbers of large-ish packages (tcl for instance) just to install
-your program that depends on liboop.
-
-I haven't compiled in the libwww adapter support - this is primarily because
-the current libwww0 package in Debian doesn't include libwwwxml, because when
-this library is compiled there is a name clash (libwww also includes
-libxmltok and libxmlparse, which are in the libxmltok1 package). It's
-difficult to compile liboop support for libwww libraries excluding libwwwxml,
-as the configure script simply links liboop-www with all of the libwww
-libraries, including libwwwxml. I'm working on a solution to this with the
-libwww maintainer. In the meantime, liboop Build-Conflicts: libwww-dev. If
-you need this support urgently, feel free to contact me and I'll hurry up
-my work on this (no real urgency at the moment, however ...)
-
- -- Timshel Knoll <timshel@debian.org> Tue, 5 Mar 2002 15:41:41 +1100
Index: 1.0-8/debian/liboop-doc.docs
===================================================================
--- 1.0-8/debian/liboop-doc.docs (revision 41)
+++ 1.0-8/debian/liboop-doc.docs (nonexistent)
@@ -1 +0,0 @@
-html
Index: 1.0-8/debian
===================================================================
--- 1.0-8/debian (revision 41)
+++ 1.0-8/debian (nonexistent)
/1.0-8/debian
Property changes:
Deleted: mergeWithUpstream
## -1 +0,0 ##
-1
\ No newline at end of property