Hi Emmanuel,
On Wed, Oct 24, 2012 at 10:51:37AM +0200, Emmanuel Promayon wrote:
> Dear Andreas,
>
> do you think it is preferable if we target inclusion in Wheezy to:
> - use Konstantinos patch or
> - try my other suggestion or
> - do nothing as it is taking too much risks to break something else?
I admit I'm no expert in this field to weight pros and cons properly.
On one hand I assume Konstantinos suggested a safe method which works
for any architecture but I have no idea about the influence regarding
the performance of the result. It also might be Konstantinos might
have simply overlooked the option to tweak the cmake file and he would
even confirm that your suggestion is better.
However, I just noticed that camitk is not yet in testing anyway so the
release team is not involved at all (we just introduced it to late after
the freeze date). So in one hand you can more or less forget my safety
means to do only a minimum change inside the source code (see the other
bug report) and even include new code if you have a new upstream version
ready and you can also apply your change for this bug - in case it does
not really work or break something else we have a couple of more shots
at this target inside unstable.
Sorry if I gave a bit picky advise under my wrong assumption that
current camitk is a candidate for Wheezy release. This also means that
you might feel free to relax the deadline a bit - but fixing bugs as
quick as possible is always a good thing.
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
