Re: best practices for dependencies version in new package

2006-07-03 Thread marciotex
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Justin Pryzby <[EMAIL PROTECTED]> writes: > On Sun, Jul 02, 2006 at 08:56:57PM -0300, [EMAIL PROTECTED] wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi. >> >> Scenario. Package is new (no version uploaded yet). Dependences is >>

Re: best practices for dependencies version in new package

2006-07-03 Thread marciotex
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Neil Williams <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: >> Scenario. Package is new (no version uploaded yet). Dependences is >> determined: dpkg-depcheck and pbuilder was used. But these tools not >> help task determine dependences versi

Re: best practices for dependencies version in new package

2006-07-03 Thread Justin Pryzby
On Sun, Jul 02, 2006 at 08:56:57PM -0300, [EMAIL PROTECTED] wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi. > > Scenario. Package is new (no version uploaded yet). Dependences is > determined: dpkg-depcheck and pbuilder was used. But these tools not > help task determine dependen

Re: best practices for dependencies version in new package

2006-07-02 Thread Neil Williams
[EMAIL PROTECTED] wrote: > Scenario. Package is new (no version uploaded yet). Dependences is > determined: dpkg-depcheck and pbuilder was used. But these tools not > help task determine dependences version. So, what best practices for > dependencies version in this package? Build-Depends should b

best practices for dependencies version in new package

2006-07-02 Thread marciotex
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. Scenario. Package is new (no version uploaded yet). Dependences is determined: dpkg-depcheck and pbuilder was used. But these tools not help task determine dependences version. So, what best practices for dependencies version in this package? W