Re: [Fink-devel] octave-forge-2004.02.12-1
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 failed, exit code 2 Failed: compiling octave-forge-2004.02.12-1 failed The latest octave-forge package (2004.02.12-2) should fix this problem. Could you 'fink selfupdate' and try again? Thanks, Chris. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] [RFC] Modification to commits procedure
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) For lower priority items, how about we commit all of the files, but not run update.sh until such time as the language teams have had a chance to do their thing--perhaps a day or two delay. Once the translations are online, we can bring all of them live simultaneously. -- Alexander Hansen Fink Documentarian [Day Job] Levitated Dipole Experiment http://www.psfc.mit.edu/LDX --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] [RFC] Modification to commits procedure
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 teams will catch up. 2) For lower priority items, how about we commit all of the files, but not run update.sh until such time as the language teams have had a chance to do their thing--perhaps a day or two delay. Once the translations are online, we can bring all of them live simultaneously. Sounds reasonable to me. -- Benjamin Reed, a.k.a. RangerRick [EMAIL PROTECTED] / http://ranger.befunk.com/ Now Playing: Conquer Your World by Excessive Force --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] [RFC] Modification to commits procedure
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 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] [RFC] Modification to commits procedure
-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 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 - -d -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (Darwin) iD8DBQFATz4zPMoaMn4kKR4RA4rKAJ0X6dNOhU7isL82HcixDr7d2WDeKACdFiQW Z+3kdJO8xu90M95lBQe/e8U= =IvGj -END PGP SIGNATURE- --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] [RFC] Modification to commits procedure
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 I'm a glutton for punishment and subscribe to -commits anyway, so I've taken responsibility for redirecting the commits messages--that way the translators get the filename and a diff to work with. -- Alexander Hansen Fink Documentarian [Day Job] Levitated Dipole Experiment http://www.psfc.mit.edu/LDX --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] [RFC] Modification to commits procedure
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? I don't follow the i18n stuff really, so this is the first I've heard of such previously discussed things. What format do I send? Do I use a prefix to the subject line? There should be doc on how that works, and it should be sent to fink-devel with a notice making it clear that all developers should read it. We get too much traffic to assume everyone reads every message and knows what to do about i18n. =) -- Benjamin Reed, a.k.a. RangerRick [EMAIL PROTECTED] / http://ranger.befunk.com/ Now Playing: Hizbollah by Ministry --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Commits procedure document link--all developers should read was [RFC] Modification to commits procedure
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 your responsibility to notify us Where is this documented? I don't follow the i18n stuff really, so this is the first I've heard of such previously discussed things. Right now it's at http://fink.useme.net/~alexander/multilingual/ . I'm in the process of migrating it over to the Fink Documentation section, so that people can modify it if they want. When I do so, I'll send out another message. What format do I send? Do I use a prefix to the subject line? There should be doc on how that works, and it should be sent to fink-devel with a notice making it clear that all developers should read it. We get too much traffic to assume everyone reads every message and knows what to do about i18n. =) It should all be covered in the Call for translation section of the aforementioned document: http://fink.useme.net/~alexander/multilingual/procedure.php#call-to- translate -- Benjamin Reed, a.k.a. RangerRick [EMAIL PROTECTED] / http://ranger.befunk.com/ Now Playing: Hizbollah by Ministry -- Alexander Hansen Fink Documentarian [Day Job] Levitated Dipole Experiment http://www.psfc.mit.edu/LDX --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: fink/perlmod/Fink ChangeLog,1.569,1.570 Validation.pm,1.106,1.107
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
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.
On 10-Mar-04, at 2:05 PM, Daniel Macks wrote:
Update of /cvsroot/fink/fink/perlmod/Fink
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29306
Modified Files:
ChangeLog Validation.pm
Log Message:
Okay Murr, we check for CVS and RCS directories during .deb validation.
Index: ChangeLog
===
RCS file: /cvsroot/fink/fink/perlmod/Fink/ChangeLog,v
retrieving revision 1.569
retrieving revision 1.570
diff -u -d -r1.569 -r1.570
--- ChangeLog 7 Mar 2004 06:09:53 - 1.569
+++ ChangeLog 10 Mar 2004 21:05:51 - 1.570
@@ -1,3 +1,7 @@
+2004-03-10 Daniel Macks [EMAIL PROTECTED]
+
+ * Validation.pm: Warn if CVS or RCS directories in a .deb
+
2004-03-07 Daniel Macks [EMAIL PROTECTED]
* Service.pm: expand_percent: allow braces to explicitly delimit
keys.
Index: Validation.pm
===
RCS file: /cvsroot/fink/fink/perlmod/Fink/Validation.pm,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -d -r1.106 -r1.107
--- Validation.pm 2 Mar 2004 01:26:11 - 1.106
+++ Validation.pm 10 Mar 2004 21:05:51 - 1.107
@@ -677,7 +677,11 @@
#
sub validate_dpkg_file {
my $dpkg_filename = shift;
- my @bad_dirs = ($basepath/src/, $basepath/man/,
$basepath/info/, $basepath/doc/, $basepath/libexec/,
$basepath/lib/locale/);
+
+ # these are used in a regex and are automatically prepended with ^
+ # make sure to protect regex metachars!
+ my @bad_dirs = ($basepath/src/, $basepath/man/,
$basepath/info/, $basepath/doc/, $basepath/libexec/,
$basepath/lib/locale/, .*/CVS/, .*/RCS/);
+
my ($pid, $bad_dir);
my $filename;
my $looks_good = 1;
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Fink-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-commits
PGP.sig
Description: This is a digitally signed message part
[Fink-devel] Re: [Fink-i18n] Last chance to vote/suggest the new i18n domain
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 decision Wow, the last vote, and at the same time the very first time I ever heard about this. It would be very helpful if you explained a) What is the domain going to be used for? b) How was that list or premade choices made? Where was this discussed, and with whom? c) I hope you did run this by at least on of my fellow project admins (I certainly didn't see it) if you plan to make this in any way an official site. If it's just an in-official site used for internal works of the I18N time; or if it's clearly marked as not being official; then of course there is no need to do this (but since it's not all clear from your mail, see also my questions a) and b), I wanted to mention this). Cheers, Max --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
