Role of library packages in Blends tasks [Was: gis branch, master, updated. 44bb6e5b478da64af8f9feb145dd349c1d7a4b34]

[Andreas Tille <andreas@an3as.eu>]

Hi Bas,

you recently updated the libgdal1 entry in the Debian GIS workstation
task (see below).  I would like to point out that it usually makes no
sense to add library packages to the tasks.  On one hand tasks are
intended to install user *applications* on the other hand developers
might interested in lib*-dev packages (which implicitly depend from the
lib* package anyway).  So I'd recommend to drop the library packages at
all (which has the side effect to decrease the maintenance effort for
the tasks).

Kind regards

          Andreas.

On Sat, Mar 08, 2014 at 11:55:47PM +0000, Bas Couwenberg wrote:
> The following commit has been merged in the master branch:
> commit 44bb6e5b478da64af8f9feb145dd349c1d7a4b34
> Author: Bas Couwenberg <sebastic@xs4all.nl>
> Date:   Sun Mar 9 00:55:43 2014 +0100
> 
>     Add libgdal-grass for gdal 1.10.1.
> 
> diff --git a/tasks/workstation b/tasks/workstation
> index 7c59648..c7e1bfd 100644
> --- a/tasks/workstation
> +++ b/tasks/workstation
> @@ -38,6 +38,8 @@ Depends:     gdal-bin
>  
>  Depends:     libgdal-dev, python-gdal
>  
> +Suggests:    libgdal1-1.9.0-grass, libgdal1-1.10.1-grass
> +

-- 
http://fam-tille.de