fink-i18n — Discussion about and translation of documentation

Re: [Fink-i18n] pt_BR translation

[Monic P. <mo...@gm...>]

On 27/02/2009, at 20:44, BABA Yoshihiko wrote:
> Welcome to the translation team! The XML system may confuse you a bit.
> You need some packages like libxslt.

I'm familiar with XML do I don't think it'll be a problem. :)

> I heard someone (Alexander?) was thinking a major change in
> documentation. Am I correct?


Hmm, is it true? I'm halfway through the User's Guide. I'd be glad to  
help with any changes you might have in mind.


Cheers,

--
MP

Re: [Fink-i18n] pt_BR translation

[BABA Y. <bab...@ma...>]

Hi,

On Feb 28, 2009, at 3:01 AM, Alexander Hansen wrote:

> Monic Polynomial wrote:
>> Hello all. I'd like to start translating Fink to pt_BR (Brazilian
>> Portuguese). I'm reading the documentation on i18n. Anything else I  
>> be
>> aware of?

Welcome to the translation team! The XML system may confuse you a bit.  
You need some packages like libxslt.

I heard someone (Alexander?) was thinking a major change in  
documentation. Am I correct?




--
BABA Yoshihiko
Urban Design Laboratory, Tokyo University
TEL: +81 (0)90 1738 7439

Re: [Fink-i18n] Some doubts in the translation o Fink documents

[José R. P. F. <jo...@us...>]

Alexander Hansen escribió:
> Monic Polynomial wrote:
>> Some doubts while translating Fink documents:
>>
>>   
> One note:  the Spanish translation is very much incomplete.
>> *****
>>

Hi.

I was the coordinator of the translation to Spanish. I am out of time 
and I do not found anyone for replace me in the Spanish Translation 
Team. Since 2005, the translation to Spanish is not working. Do not use 
the Spanish as reference :(

Sorry!


-- 
%     __o                      o__
%  _ \<_                       _>/ _
% (_)/(_)  Jos\'e Ra-DMA1-US  (_)\(_)
%^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
%          http://www.josera.net
%          http://zifra.blogalia.com
%          mailto:jo...@us...

Re: [Fink-i18n] Some doubts in the translation o Fink documents

[Alexander H. <ale...@gm...>]

Monic Polynomial wrote:
> Some doubts while translating Fink documents:
>
>   
One note:  the Spanish translation is very much incomplete.
> *****
>
> File names only encode the language but not the full locale. Brazilian  
> Portuguese has quite a few lexical differences from European  
> Portuguese (especially different words for computer-related objects/ 
> concepts), but I assume this shouldn't be a major concern... until  
> users in Portugal start complaining. ;)
>
> *****
>
> Static PHP files: should $title (PHP variable) be translated? For  
> example, in people.fr.php it was translated:
>
> $title = "Contributeurs";
>
> but it wasn't translated in people.es.php:
>
> $title = "Contributors";
>   
Go ahead and translate that, yes.
> *****
>
> Should "Fink Core Team" be translated? I've noticed that in French  
> only "Team" was translated while in Spanish the whole expression was  
> kept in English
>   
Sure; go ahead and do the translation.
> *****
>
> Fink Core Team members are out of synch between people.en.php and  
> organization.en.php
>
> *****
>
>   
That's worth a look; I'm not sure which was the last updated, but that
information can be gotten from the CVS logs.
> Cheers,
>
> --
> MP
>
>
>   

-- 
Alexander Hansen
Fink User Liaison

[Fink-i18n] Some doubts in the translation o Fink documents

[Monic P. <mo...@gm...>]

Some doubts while translating Fink documents:

*****

File names only encode the language but not the full locale. Brazilian  
Portuguese has quite a few lexical differences from European  
Portuguese (especially different words for computer-related objects/ 
concepts), but I assume this shouldn't be a major concern... until  
users in Portugal start complaining. ;)

*****

Static PHP files: should $title (PHP variable) be translated? For  
example, in people.fr.php it was translated:

$title = "Contributeurs";

but it wasn't translated in people.es.php:

$title = "Contributors";

*****

Should "Fink Core Team" be translated? I've noticed that in French  
only "Team" was translated while in Spanish the whole expression was  
kept in English

*****

Fink Core Team members are out of synch between people.en.php and  
organization.en.php

*****


Cheers,

--
MP

Re: [Fink-i18n] pt_BR translation

[Alexander H. <ale...@gm...>]

Monic Polynomial wrote:
> Hello all. I'd like to start translating Fink to pt_BR (Brazilian  
> Portuguese). I'm reading the documentation on i18n. Anything else I be  
> aware of?
>
>
> --
> MP
>
>   
Welcome! 

The main thing to note is that much of the documentation is generated
from XML source files.

-- 
Alexander Hansen
Fink User Liaison

[Fink-i18n] pt_BR translation

[Monic P. <mo...@gm...>]

Hello all. I'd like to start translating Fink to pt_BR (Brazilian  
Portuguese). I'm reading the documentation on i18n. Anything else I be  
aware of?


--
MP

[Fink-i18n] [Fwd: [cvs] web/xml/faq faq.en.xml,1.86,1.87]

[Alexander H. <ale...@gm...>]

pro forma request for translation

-------- Original Message --------
Subject: [cvs] web/xml/faq faq.en.xml,1.86,1.87
Date: Mon, 01 Sep 2008 00:48:35 +0000
From: Alexander Hansen <ale...@us...>
Reply-To: fin...@li...
To: fin...@li...
Newsgroups: gmane.os.apple.fink.cvs
Followup-To: gmane.os.apple.fink.devel

Update of /cvsroot/fink/web/xml/faq
In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv14128

Modified Files:
	faq.en.xml
Log Message:
Expand installer permissions FAQ


Index: faq.en.xml
===================================================================
RCS file: /cvsroot/fink/web/xml/faq/faq.en.xml,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -d -r1.86 -r1.87
--- faq.en.xml	30 Jul 2008 14:38:31 -0000	1.86
+++ faq.en.xml	1 Sep 2008 00:48:33 -0000	1.87
@@ -954,7 +954,11 @@
       </question>
       <answer>
         <p>This message commonly means that you've tried to run the
Fink installer as user who doesn't have administrative privileges.  Make
sure to log in at the login screen as such a user or switch to such a
user in the Finder (i.e. fast user switching) before starting the Fink
installer.</p>
-        <p>If you're having trouble even when using an admin account,
then it's likely a problem with the permissions on your top-level
directory.  Use Apple's Disk Utility (from the Utilities sub-folder in
your Applications folder), select the hard drive in question, choose the
<em>First Aid</em> tab, and press <em>Repair Disk Permissions</em>.</p>
+        <p>If you're having trouble even when using an admin account,
then it's likely a problem with the permissions on your top-level
directory.  Use Apple's Disk Utility (from the Utilities sub-folder in
your Applications folder), select the hard drive in question, choose the
<em>First Aid</em> tab, and press <em>Repair Disk Permissions</em>.  If
that doesn't work, then you may need to set your permissions manually
via:</p>
+	<codeblock>
+sudo chmod 1775 /	
+	</codeblock>
+	
       </answer>
     </faqentry>
     <faqentry name="wrong-arch">


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[Fink-i18n] TRANSLATE: Fwd: [cvs] web/xml/packaging packaging.en.xml, 1.102, 1.103

[Daniel M. <dm...@ne...>]

Modified Files:
	packaging.en.xml 
Log Message:
Appears that InstallScript runs before Files in each SplitOff

Index: packaging.en.xml
===================================================================
RCS file: /cvsroot/fink/web/xml/packaging/packaging.en.xml,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -d -r1.102 -r1.103
--- packaging.en.xml	27 Aug 2008 05:20:51 -0000	1.102
+++ packaging.en.xml	27 Aug 2008 05:44:07 -0000	1.103
@@ -3251,10 +3251,14 @@
 <p>
 During the install phase, the <code>InstallScript</code> and 
 <code>DocFiles</code> of the parent package are executed first.
-Next comes processing of the <code>SplitOff</code> and <code>SplitOff<em>N</em></code> fields. For each such field in turn, the <code>Files</code> command causes the listed files and directories
+Next comes processing of the <code>SplitOff</code> and
+<code>SplitOff<em>N</em></code> fields. For each such field in turn,
+the <code>InstallScript</code> of that field is run, and then the
+<code>Files</code> command causes the listed files and directories
 to be moved from the parent's installation directory %I to the
-current installation directory %i.  Then the <code>InstallScript</code>
-and <code>DocFiles</code> of the given <code>SplitOff</code> or <code>SplitOff<em>N</em></code> package are
+current installation directory %i.  Then the <code>DocFiles</code>
+and other Installation Phase fields of the given <code>SplitOff</code>
+or <code>SplitOff<em>N</em></code> package are
 executed.  
 </p><p>
 At this time, the <code>SplitOff</code> is processed first (if

[Fink-i18n] Translate: [cvs] web/xml/news news.en.xml,1.81,1.82

[David R. M. <dr...@fi...>]

Begin forwarded message:

> From: "David R. Morrison" <dm...@us...>
> Date: June 26, 2008 9:41:39 PM EDT
> To: fin...@li...
> Subject: [cvs] web/xml/news news.en.xml,1.81,1.82
> Reply-To: fin...@li...
>
> Update of /cvsroot/fink/web/xml/news
> In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv20405
>
> Modified Files:
> 	news.en.xml
> Log Message:
> new bindist
>
>
> Index: news.en.xml
> ===================================================================
> RCS file: /cvsroot/fink/web/xml/news/news.en.xml,v
> retrieving revision 1.81
> retrieving revision 1.82
> diff -u -d -r1.81 -r1.82
> --- news.en.xml	2 Apr 2008 03:59:52 -0000	1.81
> +++ news.en.xml	27 Jun 2008 01:41:37 -0000	1.82
> @@ -3,6 +3,30 @@
> <news lang="en">
>   <cvsid>$Id$</cvsid>
>
> +  <newsitem>
> +    <date>2008-06-26</date>
> +    <headline>New Fink release.</headline>
> +    <body>
> +      <p>
> +A new (binary) Fink release for OS X 10.5 (Leopard) is
> +<varlink url="download/index.php">available</varlink>
> + today: version 0.9.0, which can be installed on either Intel or  
> PowerPC
> +hardware.
> +The release includes source files, binary packages, and  Fink
> +installers for both kinds of hardware.
> +</p>
> +      <p>
> +Users who have already installed Fink on Leopard from source, who  
> now wish
> +to switch to the binary distribution, may do so as follows.  First,
> +run <code>fink selfupdate</code> to update to the latest version of  
> the
> +fink package manager.  Next, run <code>fink configure</code>, and  
> be sure
> +to <em>change</em> your choice about using the binary distribution  
> from No
> +to yes.  Final, run <code>fink scanpackages</code> to activate the  
> binary
> +distribution.
> +</p>
> +</body>
> +  </newsitem>
> +
> <newsitem>
> 	<date>2008-02-03</date>
> 	<headline>Mirror, mirror on the wall, will someone sponsor Fink at  
> all?</headline>
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Fink-commits mailing list
> Fin...@li...
> http://news.gmane.org/gmane.os.apple.fink.cvs

[Fink-i18n] Translate: (part 3 of 3) [cvs] web/xml/packaging packaging.en.xml, 1.100, 1.101

[David R. M. <dr...@fi...>]

Begin forwarded message:

> From: "David R. Morrison" <dm...@us...>
> Date: June 7, 2008 8:59:54 AM PDT
> To: fin...@li...
> Subject: [cvs] web/xml/packaging packaging.en.xml,1.100,1.101
> Reply-To: fin...@li...
>
> Update of /cvsroot/fink/web/xml/packaging
> In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv15584
>
> Modified Files:
> 	packaging.en.xml
> Log Message:
> final installment of this round of revisions
>
>
> Index: packaging.en.xml
> ===================================================================
> RCS file: /cvsroot/fink/web/xml/packaging/packaging.en.xml,v
> retrieving revision 1.100
> retrieving revision 1.101
> diff -u -d -r1.100 -r1.101
> --- packaging.en.xml	5 Jun 2008 03:57:57 -0000	1.100
> +++ packaging.en.xml	7 Jun 2008 15:59:52 -0000	1.101
> @@ -624,12 +624,12 @@
> </ul>
> <p>Note that a package may also install private shared libraries,  
> which
> are not intended to be linked from any other package.  In this case,  
> the
> -libraries need to go into a separate package, but a <code>Shlibs</ 
> code>
> +libraries need not go into a separate package, but a <code>Shlibs</ 
> code>
> field must still be part of the package containing shared  
> libraries.  Also,
> -maintainers should be careful not to store a final link from  
> libfoo.dylib
> +maintainers should try to avoid storing a final link from  
> libfoo.dylib
> in the main library directory <filename>%i/lib</filename>
> -(or its 64-bit equivalent), to avoid
> -having other programs accidentally link to this library.
> +(or its 64-bit equivalent), to prevent
> +other programs from accidentally linking to this library.
> </p>
> <p>
>   A maintainer who has reasons to deviate from this policy and not  
> split the
> @@ -736,21 +736,21 @@
> barN-bin as well as barN-shlibs.
> </p><p>
> When building shared libraries under major version N, it is  
> important that
> -the "install_name" of the library be <filename>%p/lib/bar.N.dylib</ 
> filename>.
> +the "install_name" of the library be <filename>%p/lib/ 
> libbar.N.dylib</filename>.
> (You can
> find the install_name by running <code>otool -L</code> on your  
> library,
> or <code>otool64 -L</code> for 64bit libraries.)  The
> actual library file may be installed at another location, such as
> </p>
> <codeblock>
> -  %i/lib/bar.N.x.y.dylib
> +  %i/lib/libbar.N.x.y.dylib
> </codeblock>
> <p>
> and your packages should create symbolic links
> </p>
> <codeblock>
> -  %i/lib/bar.N.dylib -> %p/lib/bar.N.x.y.dylib
> -  %i/lib/bar.dylib -> %p/lib/bar.N.x.y.dylib
> +  %i/lib/libbar.N.dylib -> %p/lib/libbar.N.x.y.dylib
> +  %i/lib/libbar.dylib -> %p/lib/libbar.N.x.y.dylib
> </codeblock>
> <p>from the install_name path and from the linking path to the actual
> library.  (The first will not be needed if the library is in fact
> @@ -760,7 +760,7 @@
> If the static library is also built, then it will be installed at
> </p>
> <codeblock>
> -  %i/lib/bar.a
> +  %i/lib/libbar.a
> </codeblock>
> <p>
> If the package uses libtool, these things are usually handled  
> automatically,
> @@ -775,8 +775,8 @@
> <ul>
> <li>  in package barN-shlibs:
> <codeblock>
> -  %i/lib/bar.N.x.y.dylib
> -  %i/lib/bar.N.dylib -> %p/lib/bar.N.x.y.dylib
> +  %i/lib/libbar.N.x.y.dylib
> +  %i/lib/libbar.N.dylib -> %p/lib/libbar.N.x.y.dylib
>   %i/lib/bar/N/*
>   %i/share/bar/N/*
>   %i/share/doc/barN-shlibs/*
> @@ -784,8 +784,8 @@
> <li>  in package barN:
> <codeblock>
>   %i/include/*
> -  %i/lib/bar.dylib -> %p/lib/bar.N.x.y.dylib
> -  %i/lib/bar.a
> +  %i/lib/libbar.dylib -> %p/lib/libbar.N.x.y.dylib
> +  %i/lib/libbar.a
>   %i/share/doc/barN/*
>   other files, if needed
> </codeblock></li></ul>
> @@ -808,7 +808,7 @@
> DocFiles: COPYING
> SplitOff: &lt;&lt;
>   Package: barN-shlibs
> -  Files: lib/bar.N.x.y.dylib lib/bar.N.dylib lib/bar/N
> +  Files: lib/libbar.N.x.y.dylib lib/libbar.N.dylib lib/bar/N
>   DocFiles: COPYING
> &lt;&lt;
> </codeblock>
> @@ -862,8 +862,7 @@
> </p><p>
> The BuildDependsOnly field should only be mentioned in the  
> package's .info
> file if the package contains header files, installed into
> -<filename>%i/include</filename>, and need not be declared if the  
> header
> -files are installed into another, private, location.
> +<filename>%i/include</filename> (or subdirectories thereof).
> </p><p>
> As of fink 0.20.5, "fink validate" will issue a warning for any .deb
> which contains header files and at least one dylib, and does not  
> declare
> @@ -904,11 +903,11 @@
> a declaration</p>
> <codeblock>
>   Shlibs: &lt;&lt;
> -    %p/lib/bar.1.dylib 2.1.0 bar1 (>= 1.1-2) 32
> +    %p/lib/libbar.1.dylib 2.1.0 bar1 (>= 1.1-2) 32
>   &lt;&lt;
> </codeblock>
> <p>indicates that a (32bit)
> -library with <code>-install_name</code> %p/lib/bar.1.dylib
> +library with <code>-install_name</code> %p/lib/libbar.1.dylib
> and <code>-compatibility_version</code> 2.1.0 has been installed since
> version 1.1-2 of the <em>bar1</em> package.  In addition, this  
> declaration
> amounts to  a promise
> @@ -934,7 +933,7 @@
> </p>
> <codeblock>
>   Shlibs: &lt;&lt;
> -    !%p/lib/%N/bar.1.dylib
> +    !%p/lib/%N/libbar.1.dylib
>   &lt;&lt;
> </codeblock>
> <p>The leading exclamation point indicates that this is a private  
> library,
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Fink-commits mailing list
> Fin...@li...
> http://news.gmane.org/gmane.os.apple.fink.cvs

[Fink-i18n] Translate: (part 2 of 3) [cvs] web/xml/packaging packaging.en.xml, 1.99, 1.100

[David R. M. <dr...@fi...>]

Begin forwarded message:

> From: "David R. Morrison" <dm...@us...>
> Date: June 4, 2008 8:57:59 PM PDT
> To: fin...@li...
> Subject: [cvs] web/xml/packaging packaging.en.xml,1.99,1.100
> Reply-To: fin...@li...
>
> Update of /cvsroot/fink/web/xml/packaging
> In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv8533
>
> Modified Files:
> 	packaging.en.xml
> Log Message:
> further revisions to shlibs policy documentation
>
>
> Index: packaging.en.xml
> ===================================================================
> RCS file: /cvsroot/fink/web/xml/packaging/packaging.en.xml,v
> retrieving revision 1.99
> retrieving revision 1.100
> diff -u -d -r1.99 -r1.100
> --- packaging.en.xml	2 Jun 2008 18:45:03 -0000	1.99
> +++ packaging.en.xml	5 Jun 2008 03:57:57 -0000	1.100
> @@ -598,15 +598,16 @@
>
> <section name="sharedlibs"><title>Shared Libraries</title>
> <p>
> -Fink has a new policy about shared libraries, effective in February  
> 2002.
> +Fink's policy about shared libraries became effective in February  
> 2002.
> This section of the documentation discusses version 4
> -of the policy, which coincides with the release of Fink's 0.5.0  
> distribution
> -(as well as some updates from December, 2006 to handle 64bit  
> libraries
> -and from January, 2008 to handle private shared libraries).
> +of the policy (which coincides with the release of Fink's 0.5.0  
> distribution),
> +as modified in December, 2006 to handle 64bit libraries
> +and from January, 2008 to handle private shared libraries. (In  
> addition,
> +the discussion was updated in June, 2008 to eliminate obsolete  
> references to a
> +transitional period for implementing the shared libraries policy.)
> We begin with a quick summary, and then discuss things in more detail.
> </p><p>
> -Any package which builds shared libraries and is either (1) being  
> put into
> -  the stable tree, or (2) a new package in Fink, should treat its  
> shared
> +Any package which builds shared libraries should treat its shared
>   libraries according to Fink's policy.  This means:</p>
> <ul>
> <li>   verify, using <code>otool -L</code> (or <code>otool64 -L</ 
> code> for
> @@ -621,6 +622,15 @@
>         to have
>        no other package depend on this one.</li>
> </ul>
> +<p>Note that a package may also install private shared libraries,  
> which
> +are not intended to be linked from any other package.  In this  
> case, the
> +libraries need to go into a separate package, but a <code>Shlibs</ 
> code>
> +field must still be part of the package containing shared  
> libraries.  Also,
> +maintainers should be careful not to store a final link from  
> libfoo.dylib
> +in the main library directory <filename>%i/lib</filename>
> +(or its 64-bit equivalent), to avoid
> +having other programs accidentally link to this library.
> +</p>
> <p>
>   A maintainer who has reasons to deviate from this policy and not  
> split the
>   package should explain the reasons in the DescPackaging field.
> @@ -651,22 +661,9 @@
> <itemd><p>Binaries, etc.</p></itemd></item>
> </itemtable>
>
> -<p>
> -With option 2 it is harder to upgrade an existing package:  at the  
> same
> -time as you upgrade,
> -you need to add <code>BuildDepends: foo-dev</code> to every
> -package which says <code>Depends: foo</code>.
> -One other upgrade issue to keep in mind: a package which indirectly  
> depends
> -on your package (through another package as an intermediary) may need
> -to have <code>BuildDepends: foo</code> or <code>BuildDepends: foo- 
> dev</code>
> -added to it to ensure a successful upgrade.  It is your  
> responsibility
> -to make sure that these <code>BuildDepends</code> entries are added.
> -</p>
> <p><em>The policy in detail</em></p>
> <p>
> -We now discuss things in more detail, first discussing the policy as
> -applied to newly ported software, and
> -then turning to the question of upgrading existing fink packages.   
> For
> +We now discuss things in more detail; for
> examples of the policy in action, see the  libpng, libjpeg  and
> libtiff packages.
> </p><p>
> @@ -720,9 +717,10 @@
>   BuildDepends: barN
> </codeblock>
> <p>
> -Once this system is fully in place, it will not be permitted for
> -another package to depend on barN itself.  (For backward  
> compatibility,
> -such dependencies are allowed for pre-existing packages.)  This is
> +It is not be permitted for
> +another package to depend on barN itself.  (Although there may  
> still be
> +a few such dependencies involving packages which were in place  
> prior to
> +February, 2002.)  This is
> signaled to other developers by a boolean field
> </p>
> <codeblock>
> @@ -742,7 +740,7 @@
> (You can
> find the install_name by running <code>otool -L</code> on your  
> library,
> or <code>otool64 -L</code> for 64bit libraries.)  The
> -actual library file should be installed at
> +actual library file may be installed at another location, such as
> </p>
> <codeblock>
>   %i/lib/bar.N.x.y.dylib
> @@ -754,6 +752,10 @@
>   %i/lib/bar.N.dylib -> %p/lib/bar.N.x.y.dylib
>   %i/lib/bar.dylib -> %p/lib/bar.N.x.y.dylib
> </codeblock>
> +<p>from the install_name path and from the linking path to the actual
> +library.  (The first will not be needed if the library is in fact
> +installed at the install_name path, which is becoming more common.)
> +</p>
> <p>
> If the static library is also built, then it will be installed at
> </p>
> @@ -859,7 +861,9 @@
> <p>and the reason must be given in the DescPackaging field.
> </p><p>
> The BuildDependsOnly field should only be mentioned in the  
> package's .info
> -file if the package contains header files, installed into /sw/ 
> include.
> +file if the package contains header files, installed into
> +<filename>%i/include</filename>, and need not be declared if the  
> header
> +files are installed into another, private, location.
> </p><p>
> As of fink 0.20.5, "fink validate" will issue a warning for any .deb
> which contains header files and at least one dylib, and does not  
> declare
> @@ -877,7 +881,7 @@
>   that come with a back-end library of utility functions or a program
>   that comes with plugins to handle various features. Because these
>   libraries are "private" to the package that has them, they do not
> -  require being packages with separate -shlibs
> +  require being packaged with separate -shlibs
>   or <code>BuildDependsOnly</code> SplitOffs.
> </p>
> <p><em>The Shlibs field</em>
> @@ -916,14 +920,34 @@
> Note the use of %p in the name of the library, which allows the  
> correct
> <code>-install_name</code> to be found by all users of Fink, no matter
> what prefix they have chosen.
> -</p><p>
> -When a package is updated, usually the <code>Shlibs</code> field  
> can simply
> +</p>
> +<p>When a package is updated, usually the <code>Shlibs</code> field  
> can simply
> be copied to the next version/revision of the package.  The  
> exception to
> this is if the <code>-compatibility_version</code> increases: in that
> case, the version number in the dependency information should be  
> changed
> to the current version/revision (which is the first version/revision  
> to
> provide the library with the new compatibility version number).
> -</p><p>
> +</p>
> +<p>
> +The <code>Shlibs</code>
> +entry for a private library uses a different syntax:
> +</p>
> +<codeblock>
> +  Shlibs: &lt;&lt;
> +    !%p/lib/%N/bar.1.dylib
> +  &lt;&lt;
> +</codeblock>
> +<p>The leading exclamation point indicates that this is a private  
> library,
> +and since the other information is not relevant in this case, it is
> +not included.</p>
> +<p>Note that in this example, the private shared library has been  
> placed
> +in its own subdirectory <filename>%N</filename> of the
> +<filename>%i/lib</filename> directory (which was named after the
> +package).  This is a recommended procedure for private libraries,
> +as an additional safety measure, to prevent other packages from  
> accidentally
> +linking to this library.
> +</p>
> +<p>
> <em>What to do when the major version number changes:</em>
> </p><p>
> If the major version number changes from N to M, you will create two  
> new
> @@ -946,36 +970,8 @@
> Users will then see barN and barM shuffling in and out as various  
> other
> packages are built which depend on one version or another of the  
> shared
> library, while barN-shlibs and barM-shlibs remain permanently  
> installed.
> -</p><p>
> -<em>How to upgrade an existing fink package:</em>
> -</p><p>
> -For an existing fink package which installs either static or shared
> -libraries, the best way to upgrade is to create a new version foo of
> -your package, accompanied by a new package foo-shlibs, which satisfy
> -the above policy.  If shared libraries (or any other files now  
> present
> -in foo-shlibs) were installed previously, then these new packages  
> should
> -say
> </p>
> -<codeblock>
> -  Replaces: foo (&lt;&lt; earliest.compliant.version)
> -</codeblock>
> <p>
> -so that upgrading will be transparent to users.  (You should  
> <em>not</em>
> -say "Conflicts: foo" because this will prevent the upgrade.)
> -</p><p>
> -After your upgrade, packages which say "Depends: foo" will continue  
> to
> -function normally.  However, you should contact the fink maintainers
> -of all such packages and urge them to modify their packages to say
> -"Depends: foo-shlibs, BuildDepends: foo" as soon as possible.  You  
> will
> -not be able to create new packages fooM, fooM-shlibs which  
> implement a
> -new major version of the shared library until they have done so.
> -</p><p>
> -Existing fink packages which have not used the correct install_name  
> or
> -which have not used the correct names or symbolic links for shared  
> libraries
> -must be upgraded carefully, on a case-by-case basis.  If you are
> -having trouble finding an upgrade strategy to make your packages  
> compliant
> -with the new policy, please discuss it on the fink-devel mailing  
> list.
> -</p><p>
> <em>Packages containing both binary files and libraries:</em>
> </p><p>
> When an upstream package contains both binary files and public  
> libraries, some
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Fink-commits mailing list
> Fin...@li...
> http://news.gmane.org/gmane.os.apple.fink.cvs

[Fink-i18n] Translate: (part 1 of 3) [cvs] web/xml/packaging packaging.en.xml, 1.98, 1.99

[David R. M. <dr...@fi...>]

Begin forwarded message:

> From: Daniel Macks <dm...@us...>
> Date: June 2, 2008 11:45:05 AM PDT
> To: fin...@li...
> Subject: [cvs] web/xml/packaging packaging.en.xml,1.98,1.99
> Reply-To: fin...@li...
>
> Update of /cvsroot/fink/web/xml/packaging
> In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv25353
>
> Modified Files:
> 	packaging.en.xml
> Log Message:
> document the private shared library game
>
>
> Index: packaging.en.xml
> ===================================================================
> RCS file: /cvsroot/fink/web/xml/packaging/packaging.en.xml,v
> retrieving revision 1.98
> retrieving revision 1.99
> diff -u -d -r1.98 -r1.99
> --- packaging.en.xml	1 May 2008 19:05:31 -0000	1.98
> +++ packaging.en.xml	2 Jun 2008 18:45:03 -0000	1.99
> @@ -601,7 +601,8 @@
> Fink has a new policy about shared libraries, effective in February  
> 2002.
> This section of the documentation discusses version 4
> of the policy, which coincides with the release of Fink's 0.5.0  
> distribution
> -(as well as some updates from December, 2006 to handle 64bit  
> libraries).
> +(as well as some updates from December, 2006 to handle 64bit  
> libraries
> +and from January, 2008 to handle private shared libraries).
> We begin with a quick summary, and then discuss things in more detail.
> </p><p>
> Any package which builds shared libraries and is either (1) being  
> put into
> @@ -612,7 +613,7 @@
> 64bit libraries), that
>        the install_name of each library and
>        its compatibility and current version numbers are correct </li>
> -<li>   put the shared libraries in a separate package (except for the
> +<li>   put the public shared libraries in a separate package  
> (except for the
>        links from libfoo.dylib to the install_name), and include
>        the <code>Shlibs</code> field in that package</li>
> <li>   put the headers and the final links from libfoo.dylib into a  
> package
> @@ -674,7 +675,7 @@
> are also free to build static libraries as well, if appropriate
> for their packages; or they may submit packages containing only static
> libraries if they wish.)
> -Whenever shared libraries are being built,
> +Whenever shared libraries are being built that are expected to be  
> used by other packages,
> <em>two</em> closely related fink packages should be made, named foo
> and foo-shlibs.  The shared libraries go in foo-shlibs, and the header
> files go in foo.  These two packages
> @@ -684,8 +685,10 @@
> to make more than two packages from the source, and this can be done
> using <code>SplitOff2</code>, <code>SplitOff3</code>, etc.)
> </p><p>
> -Each software package for which shared libraries can be built must  
> have
> -a <em>major version number</em> N.  The major version number is  
> only supposed
> +Each software package for which public shared libraries are built  
> must have
> +a <em>major version number</em> N, which is included in the shared
> +library's filename (for example, <filename>libbar.N.dylib</ 
> filename>).
> +The major version number is only supposed
> to change when a backwards-incompatible change in the library's API  
> has been
> made.  Fink uses the following naming convention: if the upstream name
> of the package is bar, then the fink packages are called barN and
> @@ -864,13 +867,27 @@
> future versions of fink, this warning will be expanded to cover the  
> case of
> a .deb with header files and a static library as well.)
> </p>
> +
> +<p>
> +  The goal of the Shared Library Policy is to allow assure
> +  compatibility between libraries supplied by one package and
> +  libraries or programs that use them in a different package. Some
> +  packages may have shared libraries that are not designed to be used
> +  by other packages. Common situations include a suite of programs
> +  that come with a back-end library of utility functions or a program
> +  that comes with plugins to handle various features. Because these
> +  libraries are "private" to the package that has them, they do not
> +  require being packages with separate -shlibs
> +  or <code>BuildDependsOnly</code> SplitOffs.
> +</p>
> <p><em>The Shlibs field</em>
> </p><p>
> In addition to putting the shared libraries in the correct package,  
> as of
> version 4 of this policy, you must also declare all of the shared  
> libraries
> using the <code>Shlibs</code> field.  This field has one line for each
> shared library, which contains the <code>-install_name</code> of the
> -library, the <code>-compatibility_version</code>, versioned
> +library. If the library is public, its <code>Shlibs</code> entry also
> +lists the <code>-compatibility_version</code>, versioned
> dependency information specifying the Fink package which provides
> this library at this compatibility version, and the library
> architecture.  (The library architecture may either be "32", "64", or
> @@ -961,7 +978,7 @@
> </p><p>
> <em>Packages containing both binary files and libraries:</em>
> </p><p>
> -When an upstream package contains both binary files and libraries,  
> some
> +When an upstream package contains both binary files and public  
> libraries, some
> care must be exercised in constructing fink packages.  In some cases,
> the only binary files will be things like <code>foo-config</code>  
> which
> are presumably only used at build time and never at run time.  In  
> these
> @@ -994,6 +1011,25 @@
> such time as the other package maintainers have upgraded their  
> packages
> which depend on <code>foo</code>.
> </p>
> +<p>
> +  As of fink-0.28.0 (released in January 2008), the format of
> +  the <code>Shlibs</code> entry for a "private" shared library has
> +  changed (see earlier discussion of the difference between a public
> +  and a private shared library). Note that the Shared Library Policy
> +  has always required all shared libraries to be listed; the change
> +  here is only in the syntax of the <code>Shlibs</code> field.  
> Because
> +  this type of shared library is not designed to be used by external
> +  packages, there is no need to document its compatilibity or other
> +  versioning. Instead, an exclamation-mark is used.  For example,
> +  if <filename>libquux.3.dylib</filename> is
> +  the <code>install_name</code> of a private shared library, it would
> +  be listed as follows:
> +</p>
> +<codeblock>
> +  Shlibs: &lt;&lt;
> +    !%p/lib/libquux.3.dylib
> +  &lt;&lt;
> +</codeblock>
>
> </section>
>
> @@ -2930,9 +2966,11 @@
> <em>Introduced in fink 0.11.0.</em>
> This field declares the shared libraries which are installed in the
> package.  There is one line for each
> -shared library, which contains three or four items separated by  
> whitespace:
> -the <code>-install_name</code> of the
> -library, the <code>-compatibility_version</code>, versioned
> +shared library, which contains the <code>-install_name</code> of the
> +library and information about its binary compatibility. Shared
> +libraries that are "public" (i.e., provided for use by other  
> packages)
> +have, separated by whitespace after the filename,
> +the <code>-compatibility_version</code>, versioned package
> dependency information specifying the Fink package which provides
> this library at this compatibility version, and the
> library architecture.  (The library architecture may either be "32",  
> "64", or
> @@ -2947,6 +2985,11 @@
> <code>-compatibility_version</code>
> of at least this number will always be found in later versions of this
> Fink package.
> +Shared libraries that are "private" are denoted by an exclamation  
> mark
> +preceeding the filename, and no compatilibity or versioning
> +information is given. See the <xref chapter="policy"
> +section="sharedlibs">Shared Library Policy</xref> for more
> +information.
> </p></itemd></item>
>
> <item><itemt>RuntimeVars</itemt>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Fink-commits mailing list
> Fin...@li...
> http://news.gmane.org/gmane.os.apple.fink.cvs

[Fink-i18n] Translate: [cvs] web/xml/packaging packaging.en.xml, 1.97, 1.98

[David R. M. <dr...@fi...>]

Begin forwarded message:

> From: "David R. Morrison" <dm...@us...>
> Date: May 1, 2008 12:05:37 PM PDT
> To: fin...@li...
> Subject: [cvs] web/xml/packaging packaging.en.xml,1.97,1.98
> Reply-To: fin...@li...
>
> Update of /cvsroot/fink/web/xml/packaging
> In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv18236
>
> Modified Files:
> 	packaging.en.xml
> Log Message:
> document the OS X-style additions to FHS
>
>
> Index: packaging.en.xml
> ===================================================================
> RCS file: /cvsroot/fink/web/xml/packaging/packaging.en.xml,v
> retrieving revision 1.97
> retrieving revision 1.98
> diff -u -d -r1.97 -r1.98
> --- packaging.en.xml	21 Jun 2007 14:31:26 -0000	1.97
> +++ packaging.en.xml	1 May 2008 19:05:31 -0000	1.98
> @@ -1368,6 +1368,22 @@
>  </p>
>  </itemd></item>
>
> +<item><itemt><filename>/sw/Applications</filename></itemt>
> +<itemd>
> +<p>
> +This directory is for storing OS X-style applications which are
> +launched by double-clicking rather than from the command line.
> +</p>
> +</itemd></item>
> +
> +<item><itemt><filename>/sw/Library/Frameworks</filename></itemt>
> +<itemd>
> +<p>
> +This directory is for storing OS X-style frameworks, sometimes
> +used by OS X-style applications.
> +</p>
> +</itemd></item>
> +
>  </itemtable>
>  </section>
>
>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save  
> $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http:// 
> java.sun.com/javaone
> _______________________________________________
> Fink-commits mailing list
> Fin...@li...
> http://news.gmane.org/gmane.os.apple.fink.cvs

[Fink-i18n] [Fwd: [cvs] web/xml/faq faq.en.xml,1.84,1.85]

[Alexander H. <ale...@gm...>]

Update to FAQ

-------- Original Message --------
Subject: [cvs] web/xml/faq faq.en.xml,1.84,1.85
Date: Mon, 14 Apr 2008 00:51:17 +0000
From: Alexander Hansen <ale...@us...>
Reply-To: fin...@li...
To: fin...@li...
Newsgroups: gmane.os.apple.fink.cvs
Followup-To: gmane.os.apple.fink.devel

Update of /cvsroot/fink/web/xml/faq
In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv31732

Modified Files:
	faq.en.xml
Log Message:
Add FAQ about libXrandr annoyance

Index: faq.en.xml
===================================================================
RCS file: /cvsroot/fink/web/xml/faq/faq.en.xml,v
retrieving revision 1.84
retrieving revision 1.85
diff -u -d -r1.84 -r1.85
--- faq.en.xml	30 Jun 2007 19:25:46 -0000	1.84
+++ faq.en.xml	14 Apr 2008 00:51:15 -0000	1.85
@@ -1615,7 +1615,19 @@
  preventing you from updating <code>gettext</code>.</p>
        </answer>
      </faqentry>
-
+  <faqentry name="Leopard-libXrandr">
+    <question>
+      <p>I can't install <em>gtk+2</em> on OS 10.5.2 because 
<code>/usr/X11/lib/libXrandr.2.0.0.dylib</code> is missing.</p>
+    </question>
+    <answer>
+      <p>This problem affects machines with OS 10.5.2 pre-installed.
+      There is currently a bug in Apple's X11 in that a file in it that 
is used
+    for building references 
<code>/usr/X11/lib/libXrandr.2.0.0.dylib</code>,
+    while it actually has 
<code>/usr/X11/lib/libXrandr.2.1.0.dylib</code>.</p>
+      <p>The workaround is to run the following command to fix the 
file:</p>
+    <codeblock>sudo perl -pi.bak -e 's|2.0.0|2.1.0|' 
/usr/X11/lib/libXrandr.la</codeblock>
+    </answer>
+  </faqentry>
      <faqentry name="all-others">
        <question>
          <p>I'm having issues with a package that isn't listed here.</p>


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

[Fink-i18n] [Fwd: [cvs] web/download srcdist.en.php,1.12,1.13]

[Alexander K. H. <ale...@gm...>]

Use 0.28.1

-------- Original Message --------
Subject: [cvs] web/download srcdist.en.php,1.12,1.13
Date: Mon, 17 Mar 2008 01:11:27 +0000
From: Alexander Hansen <ale...@us...>
Reply-To: fin...@li...
To: fin...@li...
Newsgroups: gmane.os.apple.fink.cvs
Followup-To: gmane.os.apple.fink.devel

Update of /cvsroot/fink/web/download
In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv21367

Modified Files:
	srcdist.en.php
Log Message:

Let's have people use 0.28.1


Index: srcdist.en.php
===================================================================
RCS file: /cvsroot/fink/web/download/srcdist.en.php,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- srcdist.en.php	8 Mar 2008 00:17:58 -0000	1.12
+++ srcdist.en.php	17 Mar 2008 01:11:24 -0000	1.13
@@ -27,13 +27,13 @@
 <? print $release_date; ?>.
 -->

-<p><EM>fink-0.28.0</EM> was officially released on 2007-11-02.</p>
+<p><EM>fink-0.28.1</EM> was officially released on 2008-3-11.</p>
 </p>
 <ul>
 <!--<li><a
 href="http://prdownloads.sourceforge.net/fink/fink-<? print
$fink_version; ?>-full.tar.gz">Fink
 <? print $release_version; ?></a> - 6786K, .tar.gz format</li>-->
-<li><a
href="http://downloads.sourceforge.net/fink/fink-0.28.0.tar.gz">fink-0.28.0</a>
- 1308K, .tar.gz format</li>
+<li><a
href="http://downloads.sourceforge.net/fink/fink-0.28.1.tar.gz">fink-0.28.1</a>
- 1304K, .tar.gz format</li>
 </ul>

 <p>
@@ -44,9 +44,9 @@
 Instructions are in the Installation document.-->
 You will also need to install the Xcode Tools (c.f. <a
href="./index.en.php" >the Quick Start page</a>).</p>
   <p>Unpack the tar.gz archive if this hasn't been done automatically,
e.g. via</p>
-<pre>tar -xvzf fink-0.28.0.tar.gz</pre>
+<pre>tar -xvzf fink-0.28.1.tar.gz</pre>

-<p>in a terminal window.  Then, in a terminal window, change to the
resulting <em>fink-0.28.0</em> directory, and use</p>
+<p>in a terminal window.  Then, in a terminal window, change to the
resulting <em>fink-0.28.1</em> directory, and use</p>
 <pre>./bootstrap</pre>
 <p>to start the boostrapping operation, which will install the Fink
base setup.</p>
 <!--akh.  I got a note from Trevor Harmon that the 0.28.0 bootstrap
automagically runs pathsetup.sh


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Fink-i18n] [Fwd: [cvs] web people.en.php,1.16,1.17]

[Alexander K. H. <ale...@gm...>]

Update to "people" page.

-------- Original Message --------
Subject: [cvs] web people.en.php,1.16,1.17
Date: Sun, 16 Mar 2008 14:45:44 +0000
From: Alexander Hansen <ale...@us...>
Reply-To: fin...@li...
To: fin...@li...
Newsgroups: gmane.os.apple.fink.cvs
Followup-To: gmane.os.apple.fink.devel

Update of /cvsroot/fink/web
In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv14716

Modified Files:
	people.en.php
Log Message:
Update people

Index: people.en.php
===================================================================
RCS file: /cvsroot/fink/web/people.en.php,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- people.en.php	23 Feb 2007 06:32:06 -0000	1.16
+++ people.en.php	16 Mar 2008 14:45:42 -0000	1.17
@@ -124,6 +124,7 @@
 <li>Hisashi Todd Fujinaka (<i>htodd</i>)</li> <!-- doc writer -->
 <li>Claudio Garguilo</li>
 <li>Michèle Garoche</li>
+<li>Andreas Gockel (<i>gecko2</i>)</li>
 <li>Jeff Horsager</li>
 <li>Felix Kühne</li>
 <li>Apostolos Karakoussis</li>
@@ -166,7 +167,6 @@
 <li>Landon Fuller (<i>landonf</i>)</li>
 <li>Paul Gaborit</li>
 <li>Stanton Gallegos (<i>stantron</i>)</li>
-<li>Andreas Gockel (<i>gecko2</i>)</li>
 <li>Sebastian Gonzalez</li>
 <li>Joe Gorse (<i>inca34</i>)</li>
 <li>Jake Goulding</li>

[Fink-i18n] [Fwd: [cvs] web/download srcdist.en.php,1.10,1.11]

[Alexander K. H. <ale...@gm...>]

Let's do pathsetup.sh, too.

-------- Original Message --------
Subject: [cvs] web/download srcdist.en.php,1.10,1.11
Date: Thu, 28 Feb 2008 02:03:50 +0000
From: Alexander Hansen <ale...@us...>
Reply-To: fin...@li...
To: fin...@li...
Newsgroups: gmane.os.apple.fink.cvs
Followup-To: gmane.os.apple.fink.devel

Update of /cvsroot/fink/web/download
In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv5283

Modified Files:
	srcdist.en.php
Log Message:

Add note to run pathsetup.sh


Index: srcdist.en.php
===================================================================
RCS file: /cvsroot/fink/web/download/srcdist.en.php,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- srcdist.en.php	11 Feb 2008 01:05:24 -0000	1.10
+++ srcdist.en.php	28 Feb 2008 02:03:48 -0000	1.11
@@ -49,7 +49,9 @@
 <p>in a terminal window.  Then, in a terminal window, change to the
resulting <em>fink-0.28.0</em> directory, and use</p>
 <pre>./bootstrap</pre>
 <p>to start the boostrapping operation, which will install the Fink
base setup.</p>
-<p>After you have installed <em>fink</em> and the other base packages,
the commands</p>
+<p>After the installation is completed, running the command</p>
+<pre>pathsetup.sh</pre>
+<p>will set up your environment for Fink.  If you open a new terminal
window after that, it will use these environment settings.  Once you
have installed <em>fink</em> and the other base packages, the commands</p>
 <pre>fink selfupdate-rsync</pre>
 <p>or</p>
 <pre>fink selfupdate-cvs</pre>


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Fink-i18n] [Fwd: [cvs] web index.en.php,1.19,1.20]

[Alexander K. H. <ale...@gm...>]

Oops--sorry this was late.

-------- Original Message --------
Subject: [cvs] web index.en.php,1.19,1.20
Date: Sun, 24 Feb 2008 04:17:41 +0000
From: Alexander Hansen <ale...@us...>
Reply-To: fin...@li...
To: fin...@li...
Newsgroups: gmane.os.apple.fink.cvs
Followup-To: gmane.os.apple.fink.devel

Update of /cvsroot/fink/web
In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv19971

Modified Files:
	index.en.php
Log Message:
Follow suggestion of dbreiser to put the X11 issues in the Status
section.  Went one better and put a note about lack of Leopard binary
installer there, too.

Index: index.en.php
===================================================================
RCS file: /cvsroot/fink/web/index.en.php,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -d -r1.19 -r1.20
--- index.en.php	18 Aug 2006 01:31:18 -0000	1.19
+++ index.en.php	24 Feb 2008 04:17:38 -0000	1.20
@@ -55,6 +55,10 @@
 Fink 0.7.2 (for OS X 10.3), 0.6.4 (for OS X 10.2),
  and 0.4.1 (for OS X 10.1) also remain available.
 </p>
+<p>
+<!-- interim -->
+<strong>10.5 Support:</strong> A binary installer for 10.5 is not yet
available. Users are encouraged to update to OS 10.5.2, via Software
Update, in order to get bugfixes and enhancements for X11.  Further
updates continue to be made available on the <a
href="http://trac.macosforge.org/projects/xquartz/wiki/Releases">XQuartz
Update Page.</a>
+      </p>

 <h1>Resources</h1>



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Fink-i18n] [Fwd: [cvs] web/download srcdist.en.php,1.9,1.10]

[Alexander K. H. <ale...@gm...>]

-------- Original Message --------
Subject: [cvs] web/download srcdist.en.php,1.9,1.10
Date: Mon, 11 Feb 2008 01:05:27 +0000
From: Alexander Hansen <ale...@us...>
Reply-To: fin...@li...
To: fin...@li...
Newsgroups: gmane.os.apple.fink.cvs
Followup-To: gmane.os.apple.fink.devel

Update of /cvsroot/fink/web/download
In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv28433

Modified Files:
	srcdist.en.php
Log Message:

Use latest fink


Index: srcdist.en.php
===================================================================
RCS file: /cvsroot/fink/web/download/srcdist.en.php,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- srcdist.en.php	3 Nov 2007 21:29:38 -0000	1.9
+++ srcdist.en.php	11 Feb 2008 01:05:24 -0000	1.10
@@ -27,23 +27,36 @@
 <? print $release_date; ?>.
 -->

-<p><EM>fink-0.27.8</EM> was officially released on 2007-11-02.</p>
+<p><EM>fink-0.28.0</EM> was officially released on 2007-11-02.</p>
 </p>
 <ul>
 <!--<li><a
 href="http://prdownloads.sourceforge.net/fink/fink-<? print
$fink_version; ?>-full.tar.gz">Fink
 <? print $release_version; ?></a> - 6786K, .tar.gz format</li>-->
-<li><a
href="http://downloads.sourceforge.net/fink/fink-0.27.8.tar.gz">fink-0.27.8</a>
- 1292K, .tar.gz format</li>
+<li><a
href="http://downloads.sourceforge.net/fink/fink-0.28.0.tar.gz">fink-0.28.0</a>
- 1308K, .tar.gz format</li>
 </ul>

 <p>
-<b>Important:</b>
+<!--<b>Important:</b>
 Don't extract the archive with StuffIt, it will corrupt some file
 names.
 Use the command line <tt>tar</tt> utility instead.
-Instructions are in the Installation document.  You also need to
install the Xcode Tools (c.f. <a href="./index.en.php" >the Quick Start
page</a>).</p>
-<p>
-Installation and usage instructions are inside the distribution
+Instructions are in the Installation document.-->
+You will also need to install the Xcode Tools (c.f. <a
href="./index.en.php" >the Quick Start page</a>).</p>
+  <p>Unpack the tar.gz archive if this hasn't been done automatically,
e.g. via</p>
+<pre>tar -xvzf fink-0.28.0.tar.gz</pre>
+
+<p>in a terminal window.  Then, in a terminal window, change to the
resulting <em>fink-0.28.0</em> directory, and use</p>
+<pre>./bootstrap</pre>
+<p>to start the boostrapping operation, which will install the Fink
base setup.</p>
+<p>After you have installed <em>fink</em> and the other base packages,
the commands</p>
+<pre>fink selfupdate-rsync</pre>
+<p>or</p>
+<pre>fink selfupdate-cvs</pre>
+
+<p>will download the package description files and patches.</p>
+
+<p>Installation and usage instructions are inside the distribution
 tarball.
 Please read them - Fink is not a one-click-and-done thing.
 The documents README, INSTALL and USAGE are provided as pure text (for
@@ -52,11 +65,6 @@
 They are also available online in the <a
 href="../doc/index.php">documentation section</a>.
 </p>
-<p>After you have installed <em>fink</em> and the other base packages,
the commands</p>
-<pre>fink selfupdate-rsync</pre>
-<p>or</p>
-<pre>fink selfupdate-cvs</pre>
-<p>will download the package description files and patches.</p>

 <p>
 To be informed of new releases, subscribe to the <a


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[Fink-i18n] [Translate] News

[BABA Y. <bab...@ma...>]

Translators,

Please translate as usual.



2008-02-04: Mirror, mirror on the wall, will someone sponsor Fink at  
all?

[Fink-i18n] News Item Trabslation, Japanese, French, (maybe German) kinda urgent :) Thanks

[David H. <dm...@us...>]

Hello, Full text included (I know it is not a diff as it is a full entry)

<newsitem>
	<date>2008-02-03</date>
	<headline>Mirror, mirror on the wall, will someone sponsor Fink at
all?</headline>
	<body>
		<p>
Every large open source project has to face the problem of
distribution and Fink is no different. We want you to get all the
files you need to build your favourite application as quickly as
possible. A mirror close to your location is a first step to achieving
that.
</p>
		<p>
We are actively working on building a reliable distribution
infrastructure consisting of mirrors sponsored by universities and
corporations.
Recently our list of mirrors had to be shortened considerably and we
need your <b>help</b> to improve its level of quality again.
</p>
		<p>
Are you a student? Are you a professor? Do you run a Data Center? Are
you a developer with free time to spare? Even if you cannot say yes to
any of those questions you still might be able to help.
All the relevant information on how to run and sponsor a mirror can be
found on the <link
url="http://wiki.finkproject.org/index.php/Fink:FinkMirrors">FinkWiki</link>.
For specific questions you can <link
url="mailto:fin...@li...">contact us</link>
directly.
</p>
		<p>
We are looking for mirrors all over the world, but specifically in
these countries:
<ul><li>United States</li><li>Japan</li><li>Germany</li><li>France</li><li>United
Kingdom</li><li>Canada</li><li>Italy</li><li>Spain</li><li>Switzerland</li><li>Australia</li></ul>
</p>
		<p>
We would like to take this opportunity to thank those who are already
providing Fink with mirrors. Without your continued support Fink would
not be able to provide the level of service it currently does. Thank
you!
</p>
	</body>
</newsitem>

Thanks

-- 
Sent from gmail so do not trust this communication.
Do not send me sensitive information here, ask for my none-gmail accounts.

"Therefore the considerations of the intelligent always include both
benefit and harm." - Sun Tzu

Re: [Fink-i18n] [translate] news

[Pierre-Henri L. <ake...@ya...>]

I updated through CVS the french xml : web/xml/news/news.fr.xml. I apologiz=
e=20
about the empty log message. I'll write one next time.
On my computer I noticed that the homepage from the french, german, spanish=
,=20
japan, and chinese are buggy : news from 2006 instead of 2008. The archive=
=20
page seems to be ok.

Cheers,

Pierre-Henri

=2D-=20
Pierre-Henri Lavigne a.k.a. =C5keson Chihiro
=46ront end developer, Fink member
http://my.opera.com/Akeson_Chihiro/

On Monday 14 January 2008 02:58:32 BABA Yoshihiko wrote:
> 2008-01-12: Fink website down
> The fink website is not functioning correctly at present. (You may
> have noticed that many of the links on this page do not function
> correctly.) The fink team is working to resolve the problem as
> quickly as possible.
>
>
> 2007-12-10: ...
> (Note: there is an X11-2.1.1.pkg release pending which will remove
> the need to patch your Xquartz. If you install X11 2.1.1 or later, do
> not apply the Xquartz patch.)
>
> --
> BABA Yoshihiko

[Fink-i18n] [translate] news

[BABA Y. <bab...@ma...>]

2008-01-12: Fink website down
The fink website is not functioning correctly at present. (You may  
have noticed that many of the links on this page do not function  
correctly.) The fink team is working to resolve the problem as  
quickly as possible.


2007-12-10: ...
(Note: there is an X11-2.1.1.pkg release pending which will remove  
the need to patch your Xquartz. If you install X11 2.1.1 or later, do  
not apply the Xquartz patch.)

--
BABA Yoshihiko

[Fink-i18n] [translate] news

[BABA Y. <bab...@ma...>]

Translators,


please translate the text below and send to me.


Update, 2007-12-11: The X11 2.1.1 release is now available on the  
Xquartz release page. Users who have already applied the  
X11-2.1.0.1.pkg and/or the patched Xquartz-1.3.0-apple-fink file from  
macosxforge.org should upgrade to 2.1.1 or greater for Fink to work  
properly. This release supercedes all previous releases, including  
the fink-specific Xquartz.





thank you
--
babayoshihiko