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

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

Re: 1 source, 2 binaries, 2 CFLAGS and cdbs

2006-06-26 Thread marciotex
"Eddy Petrişor" <[EMAIL PROTECTED]> writes: > On 6/25/06, Neil Williams <[EMAIL PROTECTED]> wrote: >> Eddy Petrişor wrote: >> >> ? I didn't say to do that. Patching the Makefiles used by autotools >> >> before cdbs runs was my point. >> > >> > Err, yes, my bad, indeed, you did not say that. >> >>

1 source, 2 binaries, 2 CFLAGS and cdbs

2006-06-24 Thread marciotex
Hi. How implement conditions following? 1) libfoo0 and libfoo0-athlon are binary packages builded from libfoo source package 2) CFLAGS for build libfoo0 are differents that for build libfoo0-athlon 3) debian/control contains libfoo0 (Architecture: any) and libfoo0-athlon (Architecture: i38

Re: Library packages and build dependencies

2006-06-17 Thread marciotex
Nikolai Lusan <[EMAIL PROTECTED]> writes: > Hi all, [cut] Hi. > I get the feeling that this should be easy to deal with by compiling the > library packages and installing them so that debhelper can find things > in the right place, I am just a little unsure on how to do this. I'm not a mentor.