Re: [Fink-devel] Updated mplayer (#1885675)

2008-03-06 Thread James Bunton
On Tue, Feb 26, 2008 at 03:28:53PM -0500, Alexander Hansen wrote:
> James Bunton wrote:
>> Hi,
>>
>> Apologies for the cross-post to fink-users, hit the wrong address book
>> entry :\
>>
>> See this tracker item:
>> https://sourceforge.net/tracker/?func=detail&atid=414256&aid=1885674&group_id=17203
>>
>> I contacted the listed maintainer on Feb 14th 2008 and have not received a
>> response. Could the tracker item please be reopened and the package
>> reconsidered for entry in Fink?
>>
>> I'm willing to step up as the maintainer and keep up with new releases,
>> etc.  Also, this package has been confirmed to build on 10.5 PPC and Intel
>> with all validation passing.
>>
>> Thanks.
>>
>> ---
>>
>> James
> The maintainer is still active--just busy.  We'll get this looked at.

Thanks.

I noticed that you mentioned in the "New packages in tracker" thread that
undeclared dependencies in packages is a concern.

This package disables explicitly all but the declared dependencies in the
ConfigureParams field.

---

James

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel


[Fink-devel] libsndfile1-1.0.17-4

2008-03-06 Thread Andreas Jenny
macbinary3.c:30:26: error: CoreServices.h: No such file or directory
make[3]: *** [macbinary3.lo] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all] Error 2
make: *** [all-recursive] Error 1
### execution of make failed, exit code 2
Removing runtime build-lock...
Removing build-lock package...
/sw/bin/dpkg-lockwait -r fink-buildlock-libsndfile1-1.0.17-4
(Reading database ... 98171 files and directories currently installed.)
Removing fink-buildlock-libsndfile1-1.0.17-4 ...
Failed: phase compiling: libsndfile1-1.0.17-4 failed

--
Package manager version: 0.28.0
Distribution version: selfupdate-cvs Sun Mar  2 23:27:31 2008, 10.4, powerpc
Mac OS X version: 10.4.11
Unable to determine Developer Tools version
gcc version: 4.0.1 (Apple Computer, Inc. build 5370)
make version: 3.80
Feedback Courtesy of FinkCommander


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel


[Fink-devel] Failed: phase compiling: dx-4.4.4-1002 failed

2008-03-06 Thread Dominique Dhumieres
On PPC (G4) OSX 10.4.11 updating to dx-4.4.4-1002 failed with:

...
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for IceConnectionNumber in -lICE... yes
checking for SmcSetProperties in -lSM... yes
checking for printf in -lxlibcon... no
checking for XCreateWindow in -lxlib... no
checking for XtVaGetValues in -lxt... yes
checking for XtVaGetValues in -lxmstatxt... no
checking for XmStringFree in -lxmstatic... no
checking for XmStringFree in -lxm... yes
checking for glXGetConfig in -lhclglx... no
checking for gluBuild2DMipmaps in -lhclglu... no
checking for glAccum in -lglwstati... no
checking for XCreateGC in -lX11... yes
checking for XtMalloc in -lXt... yes
checking for XextAddDisplay in -lXext... yes
checking for XmuAddInitializer in -lXmu... yes
checking for sqrt in -lm... yes
checking for glXGetConfig in -lGL... no
checking for gluBuild2DMipmaps in -lGLU... no
checking for XpSetImageResolution in -lXp... no
checking for XmGetDestination in -lXm... no
configure: using old version of  LESSTIF
checking for regcomp in -lREXP... no
checking whether we are using GNU glibc math... -D_GNU_SOURCE
checking for main in -lg++... no
checking for main in -ldl... no
configure: checking for TIFF support ..
checking tiff.h usability... yes
checking tiff.h presence... yes
checking for tiff.h... yes
checking tiffio.h usability... yes
checking tiffio.h presence... yes
checking for tiffio.h... yes
checking for TIFFOpen in -ltiff... no
checking if TIFF package is complete... no -- some components failed test
configure: checking for XPM support ..
checking xpm.h usability... no
checking xpm.h presence... no
checking for xpm.h... no
checking X11/xpm.h usability... yes
checking X11/xpm.h presence... yes
checking for X11/xpm.h... yes
checking for XpmReadFileToPixmap in -lXpm... no
checking if XPM package is complete... no -- some components failed test
configure: checking for HDF components ..
checking dfsd.h usability... yes
checking dfsd.h presence... yes
checking for dfsd.h... yes
checking hdf/dfsd.h usability... no
checking hdf/dfsd.h presence... no
checking for hdf/dfsd.h... no
checking for Hopen in -ldf... no
checking if HDF package is complete... no -- some components failed test
configure: checking for CDF support ..
checking cdf.h usability... no
checking cdf.h presence... no
checking for cdf.h... no
checking for CDFlib in -lcdf... no
checking if CDF package is complete... no
configure: checking for NETCDF support ..
checking netcdf.h usability... yes
checking netcdf.h presence... yes
checking for netcdf.h... yes
checking for nc_copy_att in -lnetcdf... no
checking if NETCDF package is complete... no -- some components failed test
configure: checking for ImageMagick support ..
checking for Magick-config... yes
checking magick/api.h usability... yes
checking magick/api.h presence... yes
checking for magick/api.h... yes
checking for GetImageInfo in -lMagick... no
checking if ImageMagick package is complete... no -- some components failed test
checking for getdtablesize... no
checking for getcwd... no
checking for gethostname... no
checking for gettimeofday... no
checking for mkdir... no
checking for mkfifo... no
checking for mktime... no
checking for putenv... no
checking for re_comp... no
checking for regcmp... no
checking for select... no
checking for socket... no
checking for strcspn... no
checking for strdup... no
checking for strerror... no
checking for strspn... no
checking for strstr... no
checking for strtod... no
checking for strtol... no
checking for strtoul... no
checking for uname... no
checking for trunc... no
checking for _Errno... no
checking for spawnvp... no
checking for _spawnvp... no
checking for regcomp... no
checking for sysmp... no
checking for sysconf... no
checking for pipe... no
checking for _pipe... no
checking for _popen... no
checking for popen... no
checking for _pclose... no
checking for pclose... no
checking for random... no
checking for rand... no
checking for srandom... no
checking for shmat... no
checking for getopt... no
checking for srand... no
checking for opendir... no
checking for _findfirst... no
checking for strrstr... no
checking for strcasecmp... no
checking for stricmp... no
checking for getpid... no
checking for _getpid... no
checking for unlink... no
checking for _unlink... no
checking for getlogin... no
checking for isatty... no
checking for _isatty... no
checking for setsockopt... no
checking for isnan... no
checking for finite... no
checking if RAND_MAX defined... yes
checking if signal.h defines SIGBUS... yes
checking if signal.h defines SIGKILL... yes
checking if signal.h defines SIGDANGER... no
checking if signal.h defines SIGPIPE... yes
checking if signal.h defines SIGQUIT... yes
checking for flex... flex
checking for yywrap in -lfl... no
checking for yywrap in -ll... no
checking lex output file root... lex.yy
checking whether yytext is a pointer... no
checking lex output file root... (cached) lex.yy
checking whe

Re: [Fink-devel] [Fink-users] Fink going down the drain? --> was (New packages in tracker ).

2008-03-06 Thread Josh Berkus
David,

> The question for us is more about how to deal with the tax incurred
> through raising the money. We are quite sure that our quite
> exceptional members would use a donation button if we put one up.
> PayPal already gave us clearance for that. But we do not know how to
> declare this income in the tax forms of the person who will receive
> the funds.

Then that's the reason to join SPI or SFLC Conservancy.  Both of these are 
non-profit steward organizations who will collect and hold money for fink.  
We've been doing that for PostgreSQL for the last 2 years, and will soon 
launch our own US NPO, since we have the money to pay for it.

Also, I'd recommend a non-Paypal donation option as well; a lot of OSS hackers 
avoid PayPal ever since the Abiword fiasco.

> Thank you. I will do my best to look at the SPI and SFLC. We are all
> well aware of the time we will need to spend on paperwork and meetings
> and I am mnroe than happy to take up the paperwork part.
> Would you be willing to share more of your experience with us?

Sure, but better you can ask that on the FLOSSfoundations list once you're 
subscribed.

-- 
Josh Berkus
PostgreSQL @ Sun
San Francisco

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel


Re: [Fink-devel] New packages in tracker

2008-03-06 Thread Alexander Hansen
Kevin Horton wrote:
> On 6 Mar 2008, at 10:21, Alexander Hansen wrote:
>
>> Jed Frechette wrote:
>>>
>>> Would it help the process at all if people outside the core developers
>>> went through the tracker testing and commenting on packages?
>>>
>> Yes it would.  The case of "doesn't build on ..." is easy to handle.
>> However, there are other issues to consider that require more effort to
>> address, such as whether a package autodetects and uses libraries that
>> aren't in its dependency list, which causes it to build
>> non-deterministically.  There are tools available to look at such
>> issues--but they haven't been declared as "official".
>>
>
> It would be very helpful if we could get a good list of things to 
> check when validating package submissions.  I recently received commit 
> privileges, and have not felt competent to validate package 
> submissions as I wasn't sure of the details of what I should be 
> checking.  Once we have a good list of things to check, the next step 
> should be to automate those checks and include them in "fink 
> --validate", if possible.
>
> -- 
> Kevin Horton
> Ottawa, Canada
>
>
I've been meaning to do that, but life keeps intruding.  Since I'm not 
going to have TV and network for a little longer, I may be able to whip 
something up this weekend. :-)

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel


Re: [Fink-devel] [Fink-users] Fink going down the drain? --> was (New packages in tracker ).

2008-03-06 Thread David H.
>
> Help is available from three groups:
> 1) Software in the Public Interest
> 2) Software Freedom Law Center
> 3) the open source foundations mailing list
>
Thank you, I will put some work into that, researching those possibilities.

> For (3), let me know who in Fink is leading the NPO effort and I'll subscribe
> you.
>
That would be me. Please feel free to use my email.

> My suggestion is that you either join SPI or the SFLC conservancy until you
> can raise some money.  Then you can use that money to do a real
> incorporation.
The question for us is more about how to deal with the tax incurred
through raising the money. We are quite sure that our quite
exceptional members would use a donation button if we put one up.
PayPal already gave us clearance for that. But we do not know how to
declare this income in the tax forms of the person who will receive
the funds.

> I know from bitter personal experience that in addition to
> the up-front cash and time, running a 501(c)3 in the US requires a member of
> your project to spend 50 to 100 hours a year doing paperwork, plus board
> meetings, etc.  So it's not something you want to rush into.
Thank you. I will do my best to look at the SPI and SFLC. We are all
well aware of the time we will need to spend on paperwork and meetings
and I am mnroe than happy to take up the paperwork part.
Would you be willing to share more of your experience with us?

> Oh, and for my part, I think fink is better than ever.
>
Thank you, encouraging words are always appreciated.

-d

-- 
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

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel


Re: [Fink-devel] New packages in tracker

2008-03-06 Thread Kevin Horton
On 6 Mar 2008, at 10:21, Alexander Hansen wrote:

> Jed Frechette wrote:
>>
>> Would it help the process at all if people outside the core  
>> developers
>> went through the tracker testing and commenting on packages?
>>
> Yes it would.  The case of "doesn't build on ..." is easy to handle.
> However, there are other issues to consider that require more  
> effort to
> address, such as whether a package autodetects and uses libraries that
> aren't in its dependency list, which causes it to build
> non-deterministically.  There are tools available to look at such
> issues--but they haven't been declared as "official".
>

It would be very helpful if we could get a good list of things to  
check when validating package submissions.  I recently received  
commit privileges, and have not felt competent to validate package  
submissions as I wasn't sure of the details of what I should be  
checking.  Once we have a good list of things to check, the next step  
should be to automate those checks and include them in "fink -- 
validate", if possible.

--
Kevin Horton
Ottawa, Canada



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel


Re: [Fink-devel] New packages in tracker

2008-03-06 Thread Michal Suchanek
On 06/03/2008, Martin Costabel <[EMAIL PROTECTED]> wrote:
> Alexander Hansen wrote:
>  []
>
> > With regard to TeX, we seem to have  vocal people who want a newer TeX
>  > distro but purport not to know what to do to implement it.  We should
>  > make extra sure that changing from tetex is as painless as possible, to
>  > satisfy everybody.
>
>
> Some more remarks on the tex situation:
>
>  - Fink needs, for various reasons, its own tex package. This needs to be
>  able to coexist with a tex system installed from one of the texlive
>  variants.
>  - The currently existing Fink tetex packages may be outdated, but they
>  are good enough for a lot of people. This includes myself, and I and
>  people around me are using it in our work on a daily basis. But this
>  includes also a very active group of Fink users and developers in Japan
>  who would probably object seriously if Fink suddenly switched to a less
>  well-tested new version with a completely different structure.

I can say that the Debian TeXlive based packages work for me and I
would appreciate having the same TeX version on all systems so that I
can process the same documents in the same way.
Unfortunately this is not as easy. I had to update a template that was
created for an earlier TeX version (probably TeTeX) for it to work
with the new TeX. That's because I use non-english documents that
require encoding other than Latin1. The support for different
languages has been traditionally poor and very fragile in TeX (as in
many other projects created by (only) English speaking people). Even
for different Latin scripts, CJK is probably even worse.
So the upgrade to texlive would require not only a working set of
packages but also updating all the documents and processing scripts in
Fink and perhaps an upgrade howto for various languages so that users
can port their local documents.

I suspect this is a task that cannot be completed by a single person
or even multiple people in a historically short amount time. I guess
the packages should be able to coexist in some way until problems in
the new packages are ironed out. If both TeTeX and TeXlive cannot be
reasonably installed at the same time at least packages should be
provided for both so that they can be swapped if necessary.

Thanks

Michal

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel


Re: [Fink-devel] New packages in tracker

2008-03-06 Thread Alexander Hansen
Jed Frechette wrote:
> On Mar 5, 2008, at 6:10 PM, John Ridgway wrote:
>
>   
>> ...
>> I think that's enough venting for now. I'm sorry to trouble people,
>> but I'm trying to help, and feel like I'm submitting stuff into a
>> vacuum.
>> 
>
> I'm glad you started this thread I was starting to feel the same way  
> looking at the long list of packages in the tracker, many of which  
> appear to be outdated or have never been commented on. Should I spend  
> the time and effort cleaning up the packages I've built for internal  
> use so that they can be publicly distributed or will they just sit in  
> the tracker?
>
> Don't get me wrong I'm hugely indebted to everyone who contributes to  
> Fink, you all make my life easier everyday. Which is why I want to  
> give something back and would hate to see Fink go away.
>
> Would it help the process at all if people outside the core developers  
> went through the tracker testing and commenting on packages?
>
> --
> Jed Frechette
>
> University of New Mexico Lidar Lab
> www.unm.edu/~lidar
>
>   
Yes it would.  The case of "doesn't build on ..." is easy to handle.  
However, there are other issues to consider that require more effort to 
address, such as whether a package autodetects and uses libraries that 
aren't in its dependency list, which causes it to build 
non-deterministically.  There are tools available to look at such 
issues--but they haven't been declared as "official".



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel


Re: [Fink-devel] New packages in tracker

2008-03-06 Thread Jed Frechette

On Mar 5, 2008, at 6:10 PM, John Ridgway wrote:

> ...
> I think that's enough venting for now. I'm sorry to trouble people,
> but I'm trying to help, and feel like I'm submitting stuff into a
> vacuum.

I'm glad you started this thread I was starting to feel the same way  
looking at the long list of packages in the tracker, many of which  
appear to be outdated or have never been commented on. Should I spend  
the time and effort cleaning up the packages I've built for internal  
use so that they can be publicly distributed or will they just sit in  
the tracker?

Don't get me wrong I'm hugely indebted to everyone who contributes to  
Fink, you all make my life easier everyday. Which is why I want to  
give something back and would hate to see Fink go away.

Would it help the process at all if people outside the core developers  
went through the tracker testing and commenting on packages?

--
Jed Frechette

University of New Mexico Lidar Lab
www.unm.edu/~lidar


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel


[Fink-devel] Fink going down the drain? --> was (New packages in tracker ).

2008-03-06 Thread David H.
Hello all.

First of all let me take the opportunity to welcome the discussion
around Fink, how we are being perceived as a project and what we can
improve on.
Some know me, some do not. My name is David (dmalloc) and I spend most
of my time researching how to make Fink more accessible to our users,
how to ensure that we have a working infrastructure and I also
maintain some packages (zsh, hercules, gsasl...)

I would like to confirm to everyone here that Fink, as a project, is
very much alive. We, as a core group of people, have a vested interest
in ensuring that Fink as a project can continue to exist. Right now
Fink is at a turning point, where we will seriously need to think
about making decisions on how to take things forward. That has mostly
to do with the size of the project and the many, many people involved.

We are all doing this in our spare time. The things we need to pay for
(such as domain names and the like) are paid for by us, from our money
(usually it is somone that volunteers to pick up the tab).

What we have been working on but never finished can be derived from
the wiki but has never been really publicised. If you have a look on
the wiki: http://wiki.finkproject.org/index.php/The_Fink_Wiki you will
see a section titled:
Fink Developer Network

This is our attempt at registering a not-for-profit, tax exempt
company which could help us take Fink to the next level. It would
enable us to improve our level of service, it would also enable us to
put a better system in place to acquire funds which will then benefit
the community as a whole. Right now we are struggling with that
project.
One of the reasons is money. Registering such a company, filing all
the paperwork and doing it right requires a lawyer. Lawyers are
expensive. So while the FDN exists as a registered company in the USA,
it is not fully registered yet nor tax exempt (which can take years).
The second, most predominant reason is a limitation in time. We are
spread over the globe and we are all busy in our jobs. Sitting down,
having a chat, a phone conference and getting things moved forward is
not as easy as it seems. I should know, I have been trying for a long
time.

I hope that we will get better at this, now that Leopard is out and we
have some important bits out of the way, we can once more start
focusing on this.
I apologise to any user that feels left out and not valued. I
apologise to anyone that has not had their package reviewed yet. We
value what you are doing, it is important to us and helps us move
forward.

This is an open process. Can you help with FDN? Can you help with
funds? Are you a lawyer or know one? I will make myself available and
we can, together, core team members and YOU as well, move this
forward.#

PS: Cross posted to ALL lists, please only respond to one. Thank you!

David H.
FDN Board Member
Fink Admin type of guy
-- 
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

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel


[Fink-devel] Failed: phase compiling: geomview191-shlibs-1.9.1-1001 failed

2008-03-06 Thread Dominique Dhumieres
On Intel OSX 10.5.2 installing geomview191-shlibs-1.9.1-1001 failed with:

...
ld: cycle in dylib re-exports with /usr/X11/lib/libGL.dylib
collect2: ld returned 1 exit status
make[4]: *** [libgeomview.la] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
### execution of make failed, exit code 2

TIA

Dominique

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel


Re: [Fink-devel] New packages in tracker

2008-03-06 Thread Martin Costabel
Alexander Hansen wrote:
[]
> With regard to TeX, we seem to have  vocal people who want a newer TeX 
> distro but purport not to know what to do to implement it.  We should 
> make extra sure that changing from tetex is as painless as possible, to 
> satisfy everybody.

Some more remarks on the tex situation:

- Fink needs, for various reasons, its own tex package. This needs to be 
able to coexist with a tex system installed from one of the texlive 
variants.
- The currently existing Fink tetex packages may be outdated, but they 
are good enough for a lot of people. This includes myself, and I and 
people around me are using it in our work on a daily basis. But this 
includes also a very active group of Fink users and developers in Japan 
who would probably object seriously if Fink suddenly switched to a less 
well-tested new version with a completely different structure.
- Creating new Fink packages based on texlive would be hard work. Until 
recently I think this would have been far too hard for the currently 
available manpower, because texlive is not exactly adhering to the open 
source philosophy. They don't provide source tarballs you can download 
and then simply run configure; make; make install to get a working 
system. They really want you to download the whole precompiled 
collection and install it in their way. AFAICS, recently some people 
have been creating source tarballs that can be used in the standard way. 
We could profit of this work and that of darwinports and debian in this 
respect.
- Any system-tex package has to be compatible with the Fink tex 
packages, so creating one has to be an afterthought to creating Fink tex 
packages.

I agree that the current texlive/mactex system is now sufficiently 
stable so that a Fink system-tex package using it is possible, but for 
the reasons mentioned above, I don't see it happening soon.

Another reason no one really wants to spell out clearly (but I'll do it 
anyway) is that the tetex maintainer who is also the Fink project leader 
has, for almost two years, not had enough time. Several of the core 
maintainers and developers are in the same situation or have already 
given up. I feel the same threat as John does, namely that if the 
current situation is continuing for much longer, there is a real danger 
that the whole Fink project is going down the drain.

-- 
Martin





-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel