Re: [Fink-devel] octave-forge-2004.02.12-1

2004-03-10 Thread Christian Schaffner
Hi Michael On 08.03.2004, at 21:32, Michael Kluskens wrote: fink install octave-forge gives: ... ld: warning -prebind has no effect with -bundle ld: can't locate file for: -lqhull make[2]: *** [tsearch.oct] Error 1 make[1]: *** [geometry/] Error 2 make: *** [main/] Error 2 ### execution of make

[Fink-devel] [RFC] Modification to commits procedure

2004-03-10 Thread Alexander Hansen
SInce we are now supporting 4+ different languages, I'd like to request adhering to the following guidelines when committing changes to the documentation: 1) Absolutely urgent things (bugfixes, security, etc) would be committed as we've always done, and the language teams will catch up. 2)

Re: [Fink-devel] [RFC] Modification to commits procedure

2004-03-10 Thread Benjamin Reed
Alexander Hansen wrote: SInce we are now supporting 4+ different languages, I'd like to request adhering to the following guidelines when committing changes to the documentation: 1) Absolutely urgent things (bugfixes, security, etc) would be committed as we've always done, and the language

Re: [Fink-devel] [RFC] Modification to commits procedure

2004-03-10 Thread David R. Morrison
Do we need to notify the i18n folks in some way when we make a documentation change? Or is the i18n committee monitoring fink-commits for this purpose? (probably the best idea, since people may forget to do the notification...) -- Dave ---

Re: [Fink-devel] [RFC] Modification to commits procedure

2004-03-10 Thread David H.
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 David R. Morrison wrote: snip Or is the i18n committee monitoring fink-commits for this purpose? (probably the best idea, since people may forget to do the notification...) I#d very much welcome it, if a full diff of teh changes would be sent to

Re: [Fink-devel] [RFC] Modification to commits procedure

2004-03-10 Thread Alexander Hansen
On Mar 10, 2004, at 10:51 AM, David R. Morrison wrote: Do we need to notify the i18n folks in some way when we make a documentation change? Or is the i18n committee monitoring fink-commits for this purpose? (probably the best idea, since people may forget to do the notification...) -- Dave

Re: [Fink-devel] [RFC] Modification to commits procedure

2004-03-10 Thread Benjamin Reed
David H. wrote: I#d very much welcome it, if a full diff of teh changes would be sent to fink-i18n prefixed in the ways previously discussed. We cannot ask every translator to monitor fink-commits. When you change the docs it should be your responsibility to notify us Where is this documented?

[Fink-devel] Commits procedure document link--all developers should read was [RFC] Modification to commits procedure

2004-03-10 Thread Alexander Hansen
On Mar 10, 2004, at 11:38 AM, Benjamin Reed wrote: David H. wrote: I#d very much welcome it, if a full diff of teh changes would be sent to fink-i18n prefixed in the ways previously discussed. We cannot ask every translator to monitor fink-commits. When you change the docs it should be

[Fink-devel] Re: fink/perlmod/Fink ChangeLog,1.569,1.570 Validation.pm,1.106,1.107

2004-03-10 Thread TheSin
I disagree with this action, some packages purposely include the CVS dir like my up coming SM package in ispman. for security updates... I know I'm asking for a flame but lots of debian packages use this too, just set the cvs to a release tag so it's just updates. --- TS

[Fink-devel] Re: [Fink-i18n] Last chance to vote/suggest the new i18n domain

2004-03-10 Thread Max Horn
Am 10.03.2004 um 22:57 schrieb David H.: -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 fink-i18n.info finki18n.info fink-i18n.org finki18n.org Please vote for only one. Please put down any better domain names you can come up with. I want this done by Monday, so expect a fast moving