Re: How a package will determine the dependencies

2007-11-05 Thread Justin Pryzby
On Mon, Nov 05, 2007 at 06:39:01AM -0800, varun_shrivastava wrote: Justin Pryzby-43 wrote: On Fri, Nov 02, 2007 at 08:13:22AM -0700, varun_shrivastava wrote: You could have libinput0-debug provides:libinput0. However I still think the best way is to compile with debugging symbols

Re: How a package will determine the dependencies

2007-11-05 Thread varun_shrivastava
Justin Pryzby-43 wrote: On Fri, Nov 02, 2007 at 08:13:22AM -0700, varun_shrivastava wrote: You could have libinput0-debug provides:libinput0. However I still think the best way is to compile with debugging symbols and move the symbols to separate files in /usr/lib/debug and separate

Re: How a package will determine the dependencies

2007-11-02 Thread varun_shrivastava
Justin Pryzby-43 wrote: Do you mean it adds stuff within a #ifdef to use SDL? Why is it so huge? yes it adds code not so huge under #ifdef SDL_ENABLE ... #endif Can we provide a virtual package libinput-virtual on which the applications will depend and the virtual package can

Re: How a package will determine the dependencies

2007-11-02 Thread Justin Pryzby
On Fri, Nov 02, 2007 at 08:13:22AM -0700, varun_shrivastava wrote: Justin Pryzby-43 wrote: Do you mean it adds stuff within a #ifdef to use SDL? Why is it so huge? yes it adds code not so huge under #ifdef SDL_ENABLE ... #endif Can we provide a virtual package libinput-virtual

Re: How a package will determine the dependencies

2007-11-02 Thread Justin Pryzby
On Thu, Nov 01, 2007 at 09:42:33PM -0700, varun_shrivastava wrote: hi actually the library uses g_log kind of debugging technique ie some #defines are there, so when log is enabled #defines get replaced by g_log(***), and when its disabled #defines get replaced by (void)0 But i have a

How a package will determine the dependencies

2007-11-01 Thread varun_shrivastava
hi i have a library and want to package it But it has a configuration option as --enable-debug=yes/no So i need to make 2 packages as 1) libinput0 2) libinput0-debug So now if an application uses libinput, how the $(shlibs:Depends) variable get substituted, during application package being

Re: How a package will determine the dependencies

2007-11-01 Thread Justin Pryzby
On Thu, Nov 01, 2007 at 08:57:19AM -0700, varun_shrivastava wrote: hi i have a library and want to package it But it has a configuration option as --enable-debug=yes/no So i need to make 2 packages as 1) libinput0 2) libinput0-debug I think the recommended way to do this [0] is to

Re: How a package will determine the dependencies

2007-11-01 Thread Matthew Palmer
On Thu, Nov 01, 2007 at 08:57:19AM -0700, varun_shrivastava wrote: i have a library and want to package it But it has a configuration option as --enable-debug=yes/no So i need to make 2 packages as 1) libinput0 2) libinput0-debug So now if an application uses libinput, how the

Re: How a package will determine the dependencies

2007-11-01 Thread varun_shrivastava
hi actually the library uses g_log kind of debugging technique ie some #defines are there, so when log is enabled #defines get replaced by g_log(***), and when its disabled #defines get replaced by (void)0 But i have a bigger problem thats the library has one more option of --enable-sdl=yes/no