Le 9 janv. 2005, � 15:06, David R. Morrison a �crit :
Several of you have noticed the recent changes which I've made to a number
of packages.
I may consider being in the bundle (if I dare say so).
Most of these changes ensure that the package in questionThat I understand, what I don't understand is why it is added to bluefish but not to aspell, since the only reason why bluefish builds with gcc-3.3 is because it depends on aspell, which uses C++ code. It may be that the SetCC and SetCXX variables be false on bluefish, but I need to understand why if it is, and what should be done in which case to know if it is or not.
compiles using the gcc 3.3 compiler. (The changes involve adding gcc3.3
to BuildDepends, and then either modifying the CompileScript or adding
SetCC: gcc-3.3 and SetCXX: g++-3.3 .)
That's why I've already asked for an explanation, i.e. the logic behind it - not the actions's purpose, which is very clear to me - a month ago or so, on this same list when the packaging manual was updated and it was not clear for me what when to do.
Then also what should be done on 10.2-gcc3.3 and 10.2, since bluefish works on all those trees and depends always on aspell.
Hope this time I can have one, since bluefish will release a new version on Tuesday. And thanks in advance to whomever would be kind enough to explain it.
Mich�le <http://micmacfr.homeunix.org>
PGP.sig
Description: =?ISO-8859-1?Q?Ceci_est_une_signature_=E9lectronique_PGP?=
