On Tue, Dec 20, 2011 at 08:39:51AM +0100, Magnus Therning wrote:

Den 20 dec 2011 04:23 skrev "Fabio Riga" :

...

Hello,

do we really need profiling for every installed package? We could reduce

compiling time and disk space usage by 1/3rd.

We decided a while ago to include profiling in all packages. It *is* useful to have at times, despite the additional resources it consumes. It would be easy to remove profiling from *all* packages, but having it for some but not others will increase the amount of manual work required.

Please do keep profiling libraries. Otherwise it will be really difficult for developers. Regards ppk

2011/12/20 Peter Hercek

On 12/20/2011 11:20 AM, Piyush P Kurur wrote:

...

On Tue, Dec 20, 2011 at 08:39:51AM +0100, Magnus Therning wrote:

...

Den 20 dec 2011 04:23 skrev "Fabio Riga":

...

Hello,

do we really need profiling for every installed package? We could reduce

compiling time and disk space usage by 1/3rd.

We decided a while ago to include profiling in all packages. It *is* useful to have at times, despite the additional resources it consumes. It would be easy to remove profiling from *all* packages, but having it for some but not others will increase the amount of manual work required.

Please do keep profiling libraries. Otherwise it will be really difficult for developers.

+1

We could provide it as an additional package... Anyway, it was just an idea...

On Tue, Dec 20, 2011 at 12:55:15PM +0100, Fabio Riga wrote:

...

...

...

We decided a while ago to include profiling in all packages. It *is* useful to have at times, despite the additional resources it consumes. It would be easy to remove profiling from *all* packages, but having it for some but not others will increase the amount of manual work required.

Please do keep profiling libraries. Otherwise it will be really difficult for developers.

We could provide it as an additional package... Anyway, it was just an idea...

Not a bad idea at all (like in Debian for example). Similar idea could be explored for doc as well, however I think this would mean building the "package" thrice or equivalenty generating 3 PKGBUILDS per package. (1) For the normal library (2) For the profiling version (3) for the haddock packages. On the build side (1) and (2) will require two independent builds, they will need to depend on the appropriate packages. For example if foo depends on bar then foo-lib should depend on bar-lib where as foo-lib-prof should depend on bar-lib-prof etc. Clearly it is possible as other distros (Debian) have done it but do we want to go this route ? Or is there a cleverer way that I completely miss? regards ppk