On Thu, 22 May 2008, Chris Frey wrote:
> I encourage anyone who uses or wants to use their Blackberry as a tethered
> USB modem to give the latest CVS a try. I really want feedback from
> people with various providers, so that I can have multiple, working,
> sample configurations for pppd.
I'm encouraged, and set down to try it on centos-5. It is
needful to move to autoconf-2.61 or later, and I find that Red
Hat's rawhide holds:
autoconf-2.62-1
which requires a later m4 to build, also in rawhide:
m4-1.4.11-1
Each will build on a currently updated centos 5 system, as
non-root, and install in the customary fashion.
http://www.owlriver.com/tips/non-root/
Here is a quick diff to bring the barry.spec file up to snuff
for non-versioned tarballs, simply gzipped, from a CVS co
thus:
[EMAIL PROTECTED] barry]$ cat README-rpm
#!/bin/sh
#
# pull a barry CVS, and build a fresh set of packages
#
#
# cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/barry login
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/barry \
co -P barry
cd barry
./buildgen.sh cleanall
cd ..
#
[ -e /home/herrold/rpmbuild/SOURCES/barry-0.13.tar.gz ] && \
rm -f /home/herrold/rpmbuild/SOURCES/barry-0.13.tar.gz
tar zcf /home/herrold/rpmbuild/SOURCES/barry-0.13.tar.gz barry
[ -e barry/rpm/ ] && {
cp barry/rpm/*.spec .
# sed -i -e 's/bz2/gz/g' *.spec
# sed -i -e '[EMAIL PROTECTED] [EMAIL PROTECTED] -q -n %{name} @' *.spec
[ -e barry.spec ] && {
patch -p1 < berry.patch
}
rpmbuild -ba barry.spec
}
#
#
[EMAIL PROTECTED] barry]$ diff -u ./barry/rpm/barry.spec ./barry.spec
--- ./barry/rpm/barry.spec 2008-05-28 15:02:52.000000000 -0400
+++ ./barry.spec 2008-05-28 15:55:36.000000000 -0400
@@ -25,7 +25,7 @@
Release: 1
Group: Applications/Productivity
License: GPL
-Source: %{name}-%{version}.tar.bz2
+Source: %{name}-%{version}.tar.gz
URL: http://www.netdirect.ca/downloads/barry
Vendor: Net Direct Inc.
BuildRoot: %{_tmppath}/%{name}-%{release}-%{version}-root
@@ -109,10 +109,13 @@
%endif
%prep
-%setup -q
+%setup -q -n %{name}
%build
# main tree
+#
+./buildgen.sh
+#
%{configure} --with-boost
%{__make} %{?_smp_mflags}
@@ -238,7 +241,7 @@
* Fri Aug 03 2007 Chris Frey <[EMAIL PROTECTED]> 0.8-1
- version bump
-- changed tarball to bz2
+- changed tarball to gz
* Tue May 01 2007 Chris Frey <[EMAIL PROTECTED]> 0.7-2
- added pppob to utils
[EMAIL PROTECTED] barry]$
It was too tempting -- I have named the patch: berry.patch
at the end of teh build process, one gets files like:
Wrote: /home/herrold/rpmbuild/SRPMS/barry-0.13-1.src.rpm
Wrote: /home/herrold/rpmbuild/RPMS/x86_64/libbarry-0.13-1.x86_64.rpm
Wrote: /home/herrold/rpmbuild/RPMS/x86_64/libbarry-devel-0.13-1.x86_64.rpm
Wrote: /home/herrold/rpmbuild/RPMS/x86_64/barry-util-0.13-1.x86_64.rpm
Wrote: /home/herrold/rpmbuild/RPMS/x86_64/barry-debuginfo-0.13-1.x86_64.rpm
> At this point, edit /etc/ppp/peers/barry-rogers, and *only* change the
> pty command so that it points to where your pppob is installed.
and at this point, I go: hunh? ENOREF -- How do I know, and
how can I auto-set 'where your pppob is installed'?
> My hope is that I can create binary packages for the next release,
thus my .spec file update
-- Russ herrold
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Barry-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/barry-devel
