there are at least 2 problems where help is needed:
- there are API changes in spread v4, libspread has a higher major
  version number than in v3 (2 vs. 1).
- in spread v3 we built 4 packages from source tarball:
  * spread,
  * libspread1,
  * libspread1-dev,
  * libspread-perl.
  In spread v4 tarballs the perl stuff is not longer included, so
  libspread-perl will disappear unless we build it from CPAN or from
  spread's svn (CPAN has the more recent version) in a seperate package.

Should one build a package providing
- spread,
- libspread2,
- libspread2-dev
conflicting with libspread1/libspread1-dev? And let "Debian Perl Group"
handle the libspread-perl? 

On Mon, Mar 03, 2008 at 04:04:50PM +0000, Christopher Browne wrote:
> Package: spread
> Version: 3.17.4-1
> Severity: wishlist
> 
> Spread version 4.0 was released in December 2006, but no packaging of it
> has yet been done.
> 
> -- System Information:
> Debian Release: lenny/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 2.6.22-1-686 (SMP w/2 CPU cores)
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> Shell: /bin/sh linked to /bin/bash
> 
> Versions of packages spread depends on:
> ii  adduser                       3.105      add and remove users and groups
> ii  libc6                         2.7-8      GNU C Library: Shared libraries
> 
> spread recommends no packages.
> 
> -- no debconf information
> 
> 

-- 
Kind Regards,
 Michael Mende

http://www.menole.net/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to