I´m fooling around with the packaging. It now installs with proper
udev setup on Debian etch. Debian seems to want us to use the
plugdev group, so did that. The package is also complete (installs
cli tools, lib, include, and doc in one shot.) I figure having too much is
better than not enough, until someone figures out how to do it properly
modular.
universal diff attached root produced via:
cvs diff -u >../all_in_one_debian_etch.patch
? Makefile
? Makefile.in
? aclocal.m4
? build-arch-stamp
? config.guess
? config.h
? config.h.in
? config.log
? config.status
? config.sub
? configure
? configure-stamp
? depcomp
? install-sh
? libbarry-0.pc
? libtool
? ltmain.sh
? missing
? stamp-h1
? debian/barry
? debian/barry.postinst.debhelper
? debian/barry.postrm.debhelper
? debian/barry.substvars
? debian/files
? examples/.deps
? examples/.libs
? examples/Makefile
? examples/Makefile.in
? examples/addcontact
? gui/Makefile.in
? gui/aclocal.m4
? gui/config.h.in
? gui/config.log
? gui/configure
? gui/libtool
? gui/src/Makefile.in
? man/Makefile
? man/Makefile.in
? opensync-plugin/Makefile
? opensync-plugin/Makefile.in
? opensync-plugin/aclocal.m4
? opensync-plugin/config.h
? opensync-plugin/config.h.in
? opensync-plugin/config.log
? opensync-plugin/config.status
? opensync-plugin/configure
? opensync-plugin/libtool
? opensync-plugin/stamp-h1
? opensync-plugin/src/.deps
? opensync-plugin/src/.libs
? opensync-plugin/src/Makefile
? opensync-plugin/src/Makefile.in
? opensync-plugin/src/barry_sync.loT
? src/.deps
? src/.libs
? src/Makefile
? src/Makefile.in
? src/base64.lo
? src/common.lo
? src/controller.lo
? src/data.lo
? src/error.lo
? src/ldif.lo
? src/libbarry.la
? src/packet.lo
? src/parser.lo
? src/probe.lo
? src/protocol.lo
? src/record.lo
? src/socket.lo
? src/time.lo
? src/usbwrap.lo
? src/version.lo
? tools/.deps
? tools/.libs
? tools/Makefile
? tools/Makefile.in
? tools/bcharge
? tools/breset
? tools/btool
? tools/ktrans
? tools/pppob
? tools/translate
? tools/upldif
Index: INSTALL
===================================================================
RCS file: /cvsroot/barry/barry/INSTALL,v
retrieving revision 1.2
diff -u -r1.2 INSTALL
--- INSTALL 7 Dec 2006 23:47:00 -0000 1.2
+++ INSTALL 7 Apr 2007 04:26:13 -0000
@@ -1,8 +1,8 @@
Installation Instructions
*************************
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
-Software Foundation, Inc.
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006 Free Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
@@ -10,7 +10,10 @@
Basic Installation
==================
-These are generic installation instructions.
+Briefly, the shell commands `./configure; make; make install' should
+configure, build, and install this package. The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
@@ -23,9 +26,9 @@
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
-the results of its tests to speed up reconfiguring. (Caching is
+the results of its tests to speed up reconfiguring. Caching is
disabled by default to prevent problems with accidental use of stale
-cache files.)
+cache files.
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
@@ -35,20 +38,17 @@
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
-`configure' by a program called `autoconf'. You only need
-`configure.ac' if you want to change it or regenerate `configure' using
-a newer version of `autoconf'.
+`configure' by a program called `autoconf'. You need `configure.ac' if
+you want to change it or regenerate `configure' using a newer version
+of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
- `./configure' to configure the package for your system. If you're
- using `csh' on an old version of System V, you might need to type
- `sh ./configure' instead to prevent `csh' from trying to execute
- `configure' itself.
+ `./configure' to configure the package for your system.
- Running `configure' takes awhile. While running, it prints some
- messages telling which features it is checking for.
+ Running `configure' might take a while. While running, it prints
+ some messages telling which features it is checking for.
2. Type `make' to compile the package.
@@ -78,7 +78,7 @@
by setting variables in the command line or in the environment. Here
is an example:
- ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+ ./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
@@ -87,31 +87,29 @@
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
-own directory. To do this, you must use a version of `make' that
-supports the `VPATH' variable, such as GNU `make'. `cd' to the
+own directory. To do this, you can use GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
- If you have to use a `make' that does not support the `VPATH'
-variable, you have to compile the package for one architecture at a
-time in the source code directory. After you have installed the
-package for one architecture, use `make distclean' before reconfiguring
-for another architecture.
+ With a non-GNU `make', it is safer to compile the package for one
+architecture at a time in the source code directory. After you have
+installed the package for one architecture, use `make distclean' before
+reconfiguring for another architecture.
Installation Names
==================
-By default, `make install' will install the package's files in
-`/usr/local/bin', `/usr/local/man', etc. You can specify an
-installation prefix other than `/usr/local' by giving `configure' the
-option `--prefix=PREFIX'.
+By default, `make install' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc. You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
-give `configure' the option `--exec-prefix=PREFIX', the package will
-use PREFIX as the prefix for installing programs and libraries.
-Documentation and other data files will still use the regular prefix.
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
@@ -159,7 +157,7 @@
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
-use the `--target=TYPE' option to select the type of system they will
+use the option `--target=TYPE' to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
@@ -190,12 +188,12 @@
./configure CC=/usr/local2/bin/gcc
causes the specified `gcc' to be used as the C compiler (unless it is
-overridden in the site shell script). Here is a another example:
+overridden in the site shell script).
- /bin/bash ./configure CONFIG_SHELL=/bin/bash
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
+an Autoconf bug. Until the bug is fixed you can use this workaround:
-Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
-configuration-related scripts to be executed by `/bin/bash'.
+ CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
`configure' Invocation
======================
Index: debian/changelog
===================================================================
RCS file: /cvsroot/barry/barry/debian/changelog,v
retrieving revision 1.2
diff -u -r1.2 changelog
--- debian/changelog 5 Jan 2007 03:47:25 -0000 1.2
+++ debian/changelog 7 Apr 2007 04:26:14 -0000
@@ -1,3 +1,9 @@
+barry (0.6-1) unstable; urgency=low
+ * adapted for Debian Etch. has a newer version of udev, and plugdev
+ available. Also added btool in addition to only bcharge available
+
+ -- Peter Silva <[EMAIL PROTECTED]> Fri, 06 Apr 2007 00:00:01 -0500
+
barry (0.1-2) unstable; urgency=low
* Make this work on ubuntu as well. Ubuntu has a newer version of udev
Index: debian/control
===================================================================
RCS file: /cvsroot/barry/barry/debian/control,v
retrieving revision 1.2
diff -u -r1.2 control
--- debian/control 5 Jan 2007 03:47:25 -0000 1.2
+++ debian/control 7 Apr 2007 04:26:14 -0000
@@ -10,12 +10,9 @@
Depends: udev (>= 0.056), ${shlibs:Depends}
Description: Applications for using the BlackBerry handheld on Linux
Barry is a GPL C++ library for interfacing with the RIM BlackBerry Handheld.
- It comes with a command line tool for exploring the device and for making quick
- backups. The goal of this project is to create a fully functional syncing
- mechanism on Linux.
- .
- This version only contains the bcharge utility, which provides USB charging
- capability on Linux.
+ It comes with a command line tool (btool) for exploring the device and for
+ making quick backups. The goal of this project is to create a fully
+ functional syncing mechanism on Linux.
#Package: barry-doc
#Architecture: all
Index: debian/manpages
===================================================================
RCS file: /cvsroot/barry/barry/debian/manpages,v
retrieving revision 1.1
diff -u -r1.1 manpages
--- debian/manpages 30 Dec 2006 03:04:46 -0000 1.1
+++ debian/manpages 7 Apr 2007 04:26:14 -0000
@@ -1,2 +1,3 @@
man/bcharge.1
+man/btool.1
Index: debian/rules
===================================================================
RCS file: /cvsroot/barry/barry/debian/rules,v
retrieving revision 1.3
diff -u -r1.3 rules
--- debian/rules 30 Dec 2006 03:19:05 -0000 1.3
+++ debian/rules 7 Apr 2007 04:26:14 -0000
@@ -27,6 +27,7 @@
endif
configure: configure-stamp
+
configure-stamp:
dh_testdir
# Add here commands to configure the package.
@@ -41,8 +42,8 @@
build-arch-stamp: configure-stamp
# Add here commands to compile the arch part of the package.
- #$(MAKE)
- g++-3.3 -Wall -o tools/bcharge tools/bcharge.cc -lusb
+ ./configure --prefix=/usr
+ $(MAKE)
touch build-arch-stamp
@@ -50,8 +51,8 @@
build-indep-stamp: configure-stamp
# Add here commands to compile the indep part of the package.
- #$(MAKE) doc
- touch build-indep-stamp
+ $(MAKE) doc
+ #touch build-indep-stamp
clean:
dh_testdir
@@ -59,9 +60,7 @@
rm -f build-arch-stamp build-indep-stamp #CONFIGURE-STAMP#
# Add here commands to clean up after the build process.
- #-$(MAKE) clean
-
- rm -f tools/bcharge
+ #$(MAKE) clean
dh_clean --exclude ./src/Makefile.orig
@@ -86,11 +85,11 @@
# Add here commands to install the arch part of the package into
# debian/tmp.
- #$(MAKE) install DESTDIR=$(CURDIR)/debian/barry
- install -d $(CURDIR)/debian/barry/usr/sbin
+ $(MAKE) install DESTDIR=$(CURDIR)/debian/barry
install -d $(CURDIR)/debian/barry/etc/udev/rules.d
- install tools/bcharge $(CURDIR)/debian/barry/usr/sbin
- install udev/10-blackberry.rules.Debian $(CURDIR)/debian/barry/etc/udev/rules.d/10-blackberry.rules
+ install udev/10-blackberry.rules $(CURDIR)/debian/barry/etc/udev/rules.d/10-blackberry.rules
+ sed s/"barry"/"plugdev"/g <udev/99-barry-perms >/tmp/99-barry-perms
+ install /tmp/99-barry-perms $(CURDIR)/debian/barry/etc/udev/rules.d/99-barry-perms.rules
dh_install -s
# Must not depend on anything. This is to be called by
Index: gui/INSTALL
===================================================================
RCS file: /cvsroot/barry/barry/gui/INSTALL,v
retrieving revision 1.1
diff -u -r1.1 INSTALL
--- gui/INSTALL 13 Jan 2007 07:43:12 -0000 1.1
+++ gui/INSTALL 7 Apr 2007 04:26:14 -0000
@@ -1,8 +1,8 @@
Installation Instructions
*************************
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
-Software Foundation, Inc.
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006 Free Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
@@ -10,7 +10,10 @@
Basic Installation
==================
-These are generic installation instructions.
+Briefly, the shell commands `./configure; make; make install' should
+configure, build, and install this package. The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
@@ -23,9 +26,9 @@
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
-the results of its tests to speed up reconfiguring. (Caching is
+the results of its tests to speed up reconfiguring. Caching is
disabled by default to prevent problems with accidental use of stale
-cache files.)
+cache files.
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
@@ -35,20 +38,17 @@
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
-`configure' by a program called `autoconf'. You only need
-`configure.ac' if you want to change it or regenerate `configure' using
-a newer version of `autoconf'.
+`configure' by a program called `autoconf'. You need `configure.ac' if
+you want to change it or regenerate `configure' using a newer version
+of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
- `./configure' to configure the package for your system. If you're
- using `csh' on an old version of System V, you might need to type
- `sh ./configure' instead to prevent `csh' from trying to execute
- `configure' itself.
+ `./configure' to configure the package for your system.
- Running `configure' takes awhile. While running, it prints some
- messages telling which features it is checking for.
+ Running `configure' might take a while. While running, it prints
+ some messages telling which features it is checking for.
2. Type `make' to compile the package.
@@ -78,7 +78,7 @@
by setting variables in the command line or in the environment. Here
is an example:
- ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+ ./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
@@ -87,31 +87,29 @@
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
-own directory. To do this, you must use a version of `make' that
-supports the `VPATH' variable, such as GNU `make'. `cd' to the
+own directory. To do this, you can use GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
- If you have to use a `make' that does not support the `VPATH'
-variable, you have to compile the package for one architecture at a
-time in the source code directory. After you have installed the
-package for one architecture, use `make distclean' before reconfiguring
-for another architecture.
+ With a non-GNU `make', it is safer to compile the package for one
+architecture at a time in the source code directory. After you have
+installed the package for one architecture, use `make distclean' before
+reconfiguring for another architecture.
Installation Names
==================
-By default, `make install' will install the package's files in
-`/usr/local/bin', `/usr/local/man', etc. You can specify an
-installation prefix other than `/usr/local' by giving `configure' the
-option `--prefix=PREFIX'.
+By default, `make install' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc. You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
-give `configure' the option `--exec-prefix=PREFIX', the package will
-use PREFIX as the prefix for installing programs and libraries.
-Documentation and other data files will still use the regular prefix.
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
@@ -159,7 +157,7 @@
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
-use the `--target=TYPE' option to select the type of system they will
+use the option `--target=TYPE' to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
@@ -190,12 +188,12 @@
./configure CC=/usr/local2/bin/gcc
causes the specified `gcc' to be used as the C compiler (unless it is
-overridden in the site shell script). Here is a another example:
+overridden in the site shell script).
- /bin/bash ./configure CONFIG_SHELL=/bin/bash
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
+an Autoconf bug. Until the bug is fixed you can use this workaround:
-Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
-configuration-related scripts to be executed by `/bin/bash'.
+ CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
`configure' Invocation
======================
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
