On Wed, May 28, 2008 at 04:19:10PM -0400, R P Herrold wrote:
> I'm encouraged, and set down to try it on centos-5. It is
Thanks!
> 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:
Cool idea.
> [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
Is there a technical reason for this change, or just personal preference?
> 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}
This breaks the build across versions, since each official tarball release
will contain the sources in a "barry-<version>" directory name. As it is,
the same spec file can be used for each new version as long as the
Version: field is updated.
>
> %build
> # main tree
> +#
> +./buildgen.sh
> +#
It would be great if this was conditional on the existence of configure.
If configure already exists, it shouldn't require autoconf to build.
> > 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'?
Only the binary packages will know where they installed pppob, which is
in /usr/sbin by default.
The intention was for people to test pppob, using a stock ppp options file,
copied from the source tree, so we could test and make sure it worked.
Some people might install the CVS pppob elsewhere, so I just meant, change
that part of the options file, but please test with one as close to
mine as possible. If changes are needed, I want to know.
> > My hope is that I can create binary packages for the next release,
>
> thus my .spec file update
The buildgen.sh idea is good. Thanks very much for your testing.
Were you able to get tethered modem support working on your system?
- Chris
-------------------------------------------------------------------------
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
