[boinc] 01/01: Tweaked debian README files

[Gianfranco Costamagna]

This is an automated email from the git hooks/post-receive script.

locutusofborg-guest pushed a commit to branch master
in repository boinc.

commit 50bd4f86f2c6916c40c096ca98f5d552e153c288
Author: Gianfranco Costamagna <costamagnagianfranco at yahoo.it>
Date:   Fri Feb 14 12:47:47 2014 +0100

    Tweaked debian README files
---
 debian/README.Debian |  8 --------
 debian/README.source | 17 +++++++++--------
 2 files changed, 9 insertions(+), 16 deletions(-)

diff --git a/debian/README.Debian b/debian/README.Debian
index 1e064b8..95f7982 100644
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -5,14 +5,6 @@ Debian and Ubuntu developers maintain the BOINC packages together
 on the pkg-boinc alioth.debian.org project. You may be interested
 to hear
 
- * There is a 'boinc' source package for regular clients. Additionally,
-   a 'boinc-experimental' source package provides the very latest
-   developments.
-
-   The motivation for the redundancy is because of Upstream developing
-   the BOINC client and server code asynchronously. The packaging code
-   is mostly shared between the two.
-
  * The package provides two virtual packages to help with package
    dependencies to support the employment of graphics cards with the
    computations. For NVidia this is fine, but the AMD/ATI fglrx drivers
diff --git a/debian/README.source b/debian/README.source
index 92e2626..33248a2 100644
--- a/debian/README.source
+++ b/debian/README.source
@@ -31,14 +31,11 @@ Repackaged upstream source:
  but they are tagged in the BOINC Git repository.  Anonymous Git access
  is explained on http://boinc.berkeley.edu/trac/wiki/SourceCodeGit .
  The 'boinc' source package refers to the respective release tags.
- The 'boinc-experimental' source package uses the commit of a particular
- day.  For more information see:
+ For more information see:
 
    http://boinc.berkeley.edu/trac/wiki/SourceCode
 
- Upstream's change to Git has hit us unprepared. Our traditional approach 
- was to check everything out and then prepare a tarball from it. We have
- put that approach into the script 'export-boinc' which is available in
+ We put the tarball generation into an 'export-boinc' script, which is available in
  our pkg-boinc Git repository:
 
    wget -O export-boinc \
@@ -47,10 +44,14 @@ Repackaged upstream source:
 
  It will take a considerable while to download as the final tarball yields >15MB.
  The script will take care of remove the non-DFSG files from the upstream
- tag.  Above process is integrated into debian/rules's get-orig-source target.
+ tag.  Above process is integrated into debian/get-orig-source.sh target.
 
- Since the advent of git there should be better ways, also for an improved
- communication with upstream. We are still experimenting.
+ This target can be easily called by running "uscan" in your source tree, the first
+ time will download the "boinc-v2" git repository in your parent directory, while on the
+ next runs will just perform a "git update" to retrieve new commits and new tags.
+
+ The final tarball is put on the parent directory, and can be easily imported with
+ git-import-orig ../boinc_VERSION+dfsg.orig.tar.gz
 
 
 Screen saver

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-boinc/boinc.git