Bug#762849: Package size exploded

2015-05-14 Thread Graeme Gill
Wolfgang Oertl wrote: > On the other hand, there are many Jamfiles, and just one Jambase file, > so if the latter could be adapted to support both build modes, it would > probably be easier to maintain. The Jamfile could specify what should > be a regular .a library, and what can be either. The J

Bug#762849: Package size exploded

2015-05-14 Thread Wolfgang Oertl
Am Wed, 13 May 2015 14:49:12 +1000 schrieb Graeme Gill : > Modifying Jambase is the harder and more risky approach - changing > Jamfiles is far safer and less complex. On the other hand, there are many Jamfiles, and just one Jambase file, so if the latter could be adapted to support both build mo

Bug#762849: Package size exploded

2015-05-12 Thread Graeme Gill
Wolfgang Oertl wrote: > My goal was to change as little as possible, so that until the upstream > supports that (I have been waiting quite a few months now) it can be > used in Debian. Modifying Jambase is the harder and more risky approach - changing Jamfiles is far safer and less complex. Grae

Bug#762849: Package size exploded

2015-05-12 Thread Wolfgang Oertl
Hi! Thanks for joining the thread. On Wed, 13 May 2015 09:58:02 +1000 Graeme Gill wrote: > I don't like the approach you have use at all - modifying > Jambase to make the LibraryFromObjects rule create shared libraries > is a hack - the correct approach is to change the Jamfiles to > have a "bu

Bug#762849: Package size exploded

2015-05-12 Thread Graeme Gill
Wolfgang Oertl wrote: Hi, > As a regular user of argyll this itches enough for me to dig into the > Jam build system and to try to modify it so it uses shared libraries. Currently it is an important objective of mine for the ArgyllCMS tools to be robustly portable, while executable size is a les

Bug#762849: Package size exploded

2015-05-12 Thread Wolfgang Oertl
Hi! As a regular user of argyll this itches enough for me to dig into the Jam build system and to try to modify it so it uses shared libraries. After downloading the current source package (version 1.7.0+repack) and hacking at the Jam files I have arrived at a point where it builds, with some ca

Bug#762849: Package size exploded

2015-05-09 Thread Michael Biebl
Am 25.09.2014 um 21:57 schrieb Jörg Frings-Fürst: > Hello Michael, > > first thanks for your work this and the two other bugs. > > > Am Donnerstag, den 25.09.2014, 18:45 +0200 schrieb Michael Biebl: > [...] >> The following packages will be upgraded: >> argyll >> 1 upgraded, 2 newly installed,

Bug#762849: Package size exploded

2015-05-09 Thread Michael Biebl
Am 09.05.2015 um 15:19 schrieb Jörg Frings-Fürst: > Hi, > > the major change between 1.5 and 1.6 was the build system change from > the not upstream supported gnu make back to the upstream supported jam > based system. > > With the current version the jam built system use no shared libraries. >

Bug#762849: Package size exploded

2015-05-09 Thread Jörg Frings-Fürst
Hi, the major change between 1.5 and 1.6 was the build system change from the not upstream supported gnu make back to the upstream supported jam based system. With the current version the jam built system use no shared libraries. The problem is first the almost non-existent Jam documentation and

Bug#762849: Package size exploded

2014-11-18 Thread Wolfgang Oertl
I noticed the same issue. I think it is not sensible for this package to require >50 MB disk space. Is there any compelling reason for statically linking these binaries? I don't think that there is a relevant performance increase. So, please revert this change! Just my 2¢. -- To UNSUBSCRIBE,

Bug#762849: Package size exploded

2014-09-25 Thread Michael Biebl
Am 25.09.2014 um 23:13 schrieb Michael Biebl: > for amd64 (1.6.3-1): > package size: 3,418.3 kB installed size: 52,195.0 kB > > for i386 (1.5) > package size: 3,414.2 kB installed size: 7,490.0 kB The difference between 1.5. and 1.6 seems to be, that the invididual binaries are much larger. Afai

Bug#762849: Package size exploded

2014-09-25 Thread Michael Biebl
Hi, Am 25.09.2014 um 21:57 schrieb Jörg Frings-Fürst: > Am Donnerstag, den 25.09.2014, 18:45 +0200 schrieb Michael Biebl: > [...] >> The following packages will be upgraded: >> argyll >> 1 upgraded, 2 newly installed, 0 to remove and 6 not upgraded. >> Need to get 5979 kB of archives. >> After t

Bug#762849: Package size exploded

2014-09-25 Thread Jörg Frings-Fürst
Hello Michael, first thanks for your work this and the two other bugs. Am Donnerstag, den 25.09.2014, 18:45 +0200 schrieb Michael Biebl: [...] > The following packages will be upgraded: > argyll > 1 upgraded, 2 newly installed, 0 to remove and 6 not upgraded. > Need to get 5979 kB of archives.

Bug#762849: Package size exploded

2014-09-25 Thread Michael Biebl
Package: argyll Version: 1.6.3-1 Severity: important todays upgrade presented me with The following packages will be upgraded: argyll 1 upgraded, 2 newly installed, 0 to remove and 6 not upgraded. Need to get 5979 kB of archives. After this operation, 50.2 MB of additional disk space will be us