-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Darian Lanx wrote:
Hello community.
n1.uptime.at or 62.116.87.11
My apologies, make that ns1.uptime.at
- -d
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (Darwin)
iD8DBQE/juDriW/Ta/pxHPQRA5lnAJ0VcYQDhA7XsPkcQsj/J1+l06JEggCgxOlT
sZAd7cojQ
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
Anybody have good or bad things to say about fink 0.18.0? I'd like to move
it to stable, and release 0.19.0.
I am still not so sure that the mirror setup works properly. I am not
sure, because I am getting different resu
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Ben Hines wrote:
Why remove them?
-Ben
Because we are in the middle of a documentation freeze and because the
i18n Teams will most likely grow in such a fashion that it makes sense
for them to have their own page.
- -d
-BEGIN PGP SIGNATUR
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
> 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
fi
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
jfm wrote:
_ this perpetual reindexing
is already a sufficient punishment w/o that !!! -)
Could you please expand on that statement? Not because I want to sound
snippy, but because I am interested. Of course it is our wish to have
the users (
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
welcome it, if you _could_ send changes to the fink-i18n list _prior_
We need to set this up so that the people who are working on fink itself
are given motivation to document things they are doing. If adding to
the docu
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Daniel Macks wrote:
On Tue, Mar 23, 2004 at 04:47:46PM -0500, Dave Vasilevsky wrote:
You can usually test things by simulating yourself what Fink would do.
Set these variables:
export CPPFLAGS=-I/sw/include
export LDFLAGS=-L/sw/li
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Daniel Macks wrote:
Couldn't we just say "run this script", maybe put some explanatory
comments in the script itself, and "if you need to know the details,
RTFScript"? :)
dan
Well I think youa ll know my stance on that. That would simply make us
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
TheSin wrote:
I'm about to add nice support to fink, I was thinking of a global nice
value in fink.conf like
NICE: (-20 - 20)
and then a CLi option for it like
fink -n (-20 - 20) install bundle-kde
if no nice value then nice = -20 and I whoul
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
TheSin wrote:
Just want to make sure the right person knows since I'm rarely on IRC
anymore.
[EMAIL PROTECTED] [~]$ dpkg -S /sw/man
dante: /sw/man
[EMAIL PROTECTED] [~]$ fink list dante
Information about 2890 packages read in 8 seconds.
i dan
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
TheSin wrote:
use
mandir=%i/share/man
Well I just checked and the man pages are put into the right directory:
/sw/src/root-dante-1.1.14-12/sw/share/man$ ls -la
total 0
drwxr-xr-x4 root admin 136 Mar 26 18:11 .
drwxr-xr-x4 ro
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
jfm wrote:
I don't know to which of your above pkgs you're referring here : ccrypt
or xmlsec ?
(apparently not sudo since that's not yet in 10.3).
But for both I was referring to the 10.3 version.
ccrypt is fine, just checked it. I am fixing
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
TheSin wrote:
> these are definitely from dante
>
Well, yes. But not on my system. I just tried it and it does not install
them in the main tree but in the root-blah where they belong.
I will try later, after I finished this meeting. I just can'
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Gary Kerbaugh wrote:
--enable-fndir=%p/etc/zsh/functions
--enable-site-fndir=%p/etc/zsh/site-functions
That will not work. That means, that the zsh install script tries to
install the files and directories in /sw/etc... which is plain _wrong_.
Wh
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Gary Kerbaugh wrote:
Hi David,
Hoi Mister Kerbaugh
I understand your fix; do you already know what to edit? You didn¹t have
to do this before, right? Do you know what changed? I¹ve been looking at
this since your e-mail came in but I haven¹t
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Gary Kerbaugh wrote:
on 3/27/04 12:49 PM, David H. wrote:
Hoi Mister Kerbaugh
Hoi back 'atchya,
Hoi polloi-'R-us, eh? However please, it's Gary. :-)
Well it is David then. Where I live it is not common to use the f
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
jfm wrote:
On Mar 27, 2004, at 10:39 PM, David H. wrote:
Gary Kerbaugh wrote:
As far as whether or not to include it with zsh, I have to defer
to your
experience. As I think about it, it does seem easier to make it a
separate
package. The
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Kyle Moffett wrote:
On Mar 30, 2004, at 20:56, Alexander Strange wrote:
The Gimp 2.0 isn't a ripoff because I haven't finished the package
yet. He does provide the original Gimp sources, but if the
"application bundle" contains anything else it
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Alexander K. Hansen wrote:
The homepage link titled "Submit a new Fink package" simply
leads to the SourceForge package request tracker -- which doesn't seem
to provide any obvious method for actually *submitting* a new package.
Thanks again,
-
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
I always thought this is a bad idea that
invites to produce a lot of non-tested packages. Why not just make two
clean info files?
Because it is a matter of scalability. When you have a piece of software
that supports ma
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
Did you test wether this is really faster? I doubt that it's true. The
parsing of variants and the creation of the virtual multiple packages is
probably slower than the parsing of multiple but simpler info files.
Yes I d
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Jeff Whitaker wrote:
All: I'm working on a new r-base package which will include R built as a
framework and R.app (in addition to the command line X11 version of R). I
went back and re-read the thread on .apps in Fink, but it didn't seem like
th
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
On the Apple opensource software web page
http://www.apple.com/downloads/macosx/unix_open_source/ which every Mac
owner can find only two clicks away from their Apple menu, there is a
link to Fink, but only to version 0.6
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Alexander K. Hansen wrote:
Maybe it's a missing dependency on freetype-shlibs: that's where the
libraries should be.
Actually, if he is looking for a _static_ library there should be a -dev
splittoff including the headers AND the static librar
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
ASARI Takashi wrote:
We made w3m 1.5.1 's info files, and sent it to the original maintainer.
A month has passed, but we get no reply from him.
Can we take him over?
w3m 1.5 has i18n support, so we really need it.
I guess that is fine. Unless t
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Christian Schaffner wrote:
I do nto think that anything but true _shells_ should be in that
category.
I couldn't find any discussion about that (nor docu) but i might have
missed something. I am not sure what to do in this case. Please advi
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Ben Hines wrote:
>The old style is extremely deprecated.
^^^
When did we decide on that? Since I was not reading the mailing lists
for a bit last wekk (was very busy), I might have overlooked the
discussion, but I
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Randal L. Schwartz wrote:
"Peter" == Peter O'Gorman <[EMAIL PROTECTED]> writes:
Peter> Yeah, it was the top news item on fink's home page for a while. It is
Peter> still on the front page though.
Thanks... you mean I have to read the news? :) :)
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
but this principle has always been
more a pious wish than reality.
Could you explain in more detail what you mean?
Thank you.
- -d
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFAtz1RPMoaMn4kKR4RAxHSAJ9
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Langhoff (NZL) wrote:
Is this within fink policy? What alternatives do I have in making this
module compliant?
No. You are not allowed to install _anything_ outside of /sw-
There is one exception which is some special case when handling A
a) Contact the CVS guys and tell them to fix this
Already done. CURL does not accept self signed SSL certs as it seems. I
contacted them a long time ago.
b) In the meantime, if you have a copy of the source which you
definitely know is safe, post that somewhere safe and change the source
URL of
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Daniel Macks wrote:
| I just patched fink in CVS HEAD to check MD5 checksum as each source
| tarball is downloaded and treat a mismatch as a download failure. For
| the end-user, that means if the download process succeeds but gets the
| incorrect
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Min Xu wrote:
| Hi,
|
| I recently found my newly installed fink was crashing because I have
installed
| some old version of libfreetype in /usr/local by iInstaller. This
| makes me wondering
| should fink restrict it is search path?
/usr/local is
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
| Has anyone else noticed that the master rsync mirror doesn't respond any
| more and that - apart from two Japanese URLs - the other rsync mirrors
| don't seem to synchronize currently?
|
| I ran a little check over the rsyn
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Remi Mommsen wrote:
| Hi,
|
| Long time ago (9/5/03) I notified the maintainer (cc'd) that I believe
| that this package cannot be distributed by fink (at least not under
| GPL). Seeing the cvs commit message, I'm surprised that it is still
| there
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Blair Zajac wrote:
| I have the jove.info package which is a tiny version of Emacs, which I
| like because it starts up fast.
|
| It has a global directory /var/tmp/jove where it dumps recover and
| temporary files, unlike vi's .swp files which are
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Corey Halpin wrote:
|
|
| There seem to be only three packages (aside from mine) that depend on
| any of these things (msmtp, xmlsec, and gsasl). I'll contact their
| maintainers to notify them of this change.
|
All three are my packages :)
How
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Kevin Horton wrote:
| I'm communicating with a fink user on the MaxOSXHints forum:
|
| http://forums.macosxhints.com/showthread.php?p=133778
|
| He can't install epiphany. It seems that epiphany depends on
| xml-parser-pm, yet that pm was removed
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Dear community.
I have recently be looking more and more into bittorrent. I do believe
that sharing resources now a days for the benefit of the whole community
is a good thing. I was wondering if the Fink community was interested in
a bittorrent di
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
jfm wrote:
Actually this is one thing I would veto strongly. There is no valid
technical reason for more than one (unified) patch file.
- -d
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.3.6 (Darwin)
iD8DBQFA/WWhPMoaMn4kKR4RA7H1AJ9tG+V8paaZJeSbF
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Benjamin Reed wrote:
| David H. wrote:
|
|> jfm wrote:
|>
|> |
|> | There are probably 2 different issues: one is that in some cases it may
|> | be clearer or more convenient to use several different 'patchfiles'
|&g
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello.
Looking at Fink I get:
fink install soap-lite-ssl-pm581
/usr/bin/sudo /sw/bin/fink install soap-lite-ssl-pm581
Information about 3675 packages read in 3 seconds.
fink needs help picking an alternative to satisfy a virtual dependency.
The ca
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Lars Rosengreen wrote:
| The Darcs package I maintain comes with a bash completion script that
| can be installed in %p/etc/bash_completion.d/ . Do you think it is
| appropriate for me to put things in this directory without depending on
| the ba
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Blair Zajac wrote:
| Hi Justin,
|
| The Compress::Zlib package currently compiles and links against it's own
| private copy of zlib 1.1.4. This seems to be a waste of disk and memory
| space when Mac OS X 103.3 comes with the same version of zlib
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Blair Zajac wrote:
| Daniel Macks wrote:
|
|> On Thu, Jul 29, 2004 at 04:13:17PM -0700, Blair Zajac wrote:
|>
|>> Daniel Macks wrote:
|>>
|>>> On my 10.3.4 machine, I have /usr/lib/libz.1.1.3.dylib
|>>
|>>
|>> Funny, I was looking at the header fil
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Daniel Macks wrote:
| The 'fink checksums' mode was added two years ago when we first
| started requiring MD5 for source tarballs. The code implementing it is
| marked:
|
| # HACK HACK HACK
| # This is to be removed soon again, only a temporary
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Michèle Garoche wrote:
| Then I'm not sure colors may be suitable for color-blind people, though
| I'm in this category and have no problem with them, but there are many
| different way of being color-blind.
|
maybe it is a good idea to follow thi
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Kevin Horton wrote:
|
| There must be many other unstable users who have Fink 0.22.0, and they
| need to be told what to do to restore selfupdate functionality. I
| hesitate to post something myself, as I'm not a core developer, and I
| don't have
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Enigmail
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.3.6 (Darwin)
iD8DBQFBLlUuPMoaMn4kKR4RA176AJ4peREbbO6QwDd74eHcUEasLgMFGACbBbSz
pWBvBJKWyCzeGPOjSDRdPW4=
=BqKp
-END PGP SIGNATURE-
--- Begin Message ---
Hi Again (this is LasVegas off i
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Martin Costabel wrote:
| Do we really have a developer "planetmirror"? There is a stale cvs lock
| by this user in
/cvsroot/fink/dists/10.2-gcc3.3/unstable/main/finkinfo/text
|
Yes we do. It should be read only account for the Australian Master mir
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Jim White wrote:
| Martin Costabel wrote:
|
|> David R. Morrison wrote:
|>
|> []
|>
|>>> (3) The problems with octave, singular-libfac and others that cannot
|>>> be built with Apple's latest g++-3.3 are too fresh in the discussion
|>>> to have to
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Benjamin Reed wrote:
| Darian Lanx wrote:
|
|> More of a philosophical question. Should the code not try to pick the
|> _latest_ JVM that is present,. Thus most likely the one with the most
|> features and the one a common user would be using?
|
|
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Christian Schaffner wrote:
| Dear Fink Users and Developers
|
|
| Thanks to the help of bbraun and dmacks i just committed a new feature
| for fink. You can now tell fink to try to download pre-compiled binary
| packages from the binary distributio
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Daniel Macks wrote:
| On Wed, Oct 13, 2004 at 12:09:05AM +0200, David H. wrote:
|
|>Christian Schaffner wrote:
|>|
|>| Thanks to the help of bbraun and dmacks i just committed a new feature
|>| for fink. You can now tell fink to try
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Blair Zajac wrote:
| Apache 2.0.50 is still in Fink and there have been a number of security
| issues fixed in 2.0.51 and 2.0.52.
|
|
| So I'm thinking we should update Apache and then get Subversion up to
| 1.1.0.
|
Even though I might be repeatin
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Kevin Walzer wrote:
| I've been away from Fink for awhile, but after downloading the latest
| upgrade I noticed that TexShop is now a Fink package. Does this mean
| that there is now a process for packaging app bundles? When Dave
| Morrison asked m
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Kevin Horton wrote:
|
| It certainly would be nice to have fink automatically deal with this
| situation. I have seen discussions before about various ways to do
| this, but no one was ever able to come up with a perfect solution, so
| nothing is
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello.
As I am currently being asked to do two different things and I have not
fully decided yet how to set the paths, the fink supplied zsh package
will be broken until Monday most likely. Please do accept my apologies
for this.
Thanks
- -d
-B
William Scott wrote:
The following construct prepends the 38 function directories and
subdirectories revision 13 creates to the $fpath array without
clobbering what the user might already have:
fpath=( $(print /sw/share/zsh/**/*(/) ) $fpath )
but if you configure it the default way, it only needs
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
| 1. I've made a modification to the new UseBinaryDist stuff, introducing
| a flag "--compile-from-source" in addition to the flag
| "--use-binary-dist". My new flag will disable the use of the binary
| distribution for tha
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Becky Bendick wrote:
| Thanks for the advice.
You are most welcome.
Please note that -fabi-version=0 is just a shortcut which means "select the
latest G++ ABI version that is present". Currently there are ABI version 1 and
ABI version 2. You should
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Kurt Schwehr wrote:
| Looks like my emails are not getting through to the
| fink lists. Maybe these two links will get through.
| I would like to get some discussion going about what
| is the best way to deploy fink to a large number of
| machines
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Peter O'Gorman wrote:
| Chris Zubrzycki wrote:
|
| | Any thoughts/suggestions?
|
| Well, we need the new gettext, I agree, but we also need for users to be
| able to run a successful selfupdate and update-all. It does not seem that
| the package wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David R. Morrison wrote:
| Lars,
|
| Thanks for raising this issue. It has come up before, but it has perhaps
| not received the attention it deserves.
|
| My reading of the links you provided suggests that you are correct: we may
| not link GPL'd soft
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Vasilevsky wrote:
>
> On Mar 16, 2005, at 2:39 PM, Lars Rosengreen wrote:
>
>> Yes, I think we do. I'll try to construct a list of packages that may
>> be affected.
>
>
> Thanks Lars.
>
> I guess once we have this, for each package we'll nee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Macks wrote:
> On Sun, Mar 27, 2005 at 04:48:04PM -0800, Trevor Harmon wrote:
>
>>On Mar 27, 2005, at 6:22 AM, David H. wrote:
>>
>>>Yes, ignoring this bullshit licensing issue all together. Four
>>>highly p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin Reed wrote:
> David H. wrote:
>
>> no, I am not. That are exactly the words that they told me. The
>> likelyhood
>> that we will end up in court because we "violate" the GPL is about 0.
>> Not to
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David R. Morrison wrote:
>
> On Mar 28, 2005, at 10:08 AM, David H. wrote:
>
>> And yes, I also think that we should not adopt a policy or attitude
>> where we
>> try to go out of our way just because there "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David R. Morrison wrote:
> I've begun the implementation of the new license policy by re-licensing
> all of the packages that Lars listed in the stable/crypto category,
> re-licensing them in all four active trees. (I made them all Restrictive,
> but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Zanker wrote:
> Fresh install of Tiger, Xcode 2.0, latest fink. gnupg fails to build
> with the following error:
>
>
>>if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../include -I../intl
>>-no-cpp-precomp -I/sw/include -g -O2 -Wall -MT ttyio.o -M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello guys.
Could we lock during a selfupdate?
When a slow CVS selfupdate runs and you try to install "fink install fink",
you will get errors like these:
"Reading package info...can't open
/sw/fink/dists/unstable/main/finkinfo/sci/nco.info: No such
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Sachs wrote:
> Apple has released the scripts I've been using for my Fink builds under
> the GPL. It's in CVS under the 'scripts' module. Announcement below.
> Enjoy!
>
>
> A system for performing builds of the entire Fink system and an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FranÃois Giron wrote:
> Hello,
> I transmit here the detail concerning the failure of the
> installation of zsh.
>
>
>utils.c: In function 'adjustwinsize':
>utils.c:1000: warning: implicit declaration of function 'ioctl'
>utils.c: At top level:
>util
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hehe :)
Generating notification message...
Traceback (most recent call last):
File "/cvsroot/fink/CVSROOT/syncmail", line 433, in ?
main()
File "/cvsroot/fink/CVSROOT/syncmail", line 426, in main
contextlines, fromhost, replyto)
File "/c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin Horton wrote:
> On 2 Jul 2005, at 10:26, Peter O'Gorman wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Kevin Horton wrote:
>> |
>> | I don't know what to call the new tree - I originally thought that
>> | "testing" could work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Sachs wrote:
> On Jul 2, 2005, at 07:26, Peter O'Gorman wrote:
>
Apart from all this, will Apple gift us the necessary infrastructure to do
this? I doubt it. That means we will have to focus a lot on getting the
necessary environment setup p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello guys.
I have just installed Fink HEAD, so that is about 30 seconds old.
The validation for the bison sources is:
openssl sha1 /sw/src/bison-2.1.tar.gz
SHA1(/sw/src/bison-2.1.tar.gz)= b236923e7d4909c6fd8873ac87431833fa45069b
That file has been
Hello fans.
For a long time it has been known that the algorithm we choose your
"closest" mirror by, might not be the best one. Here is a new idea and I
hope you will leave you comments for me.
It would be quite trivial to publish DNS LOC records for every mirror
that finkmirrors has to off
Chris Zubrzycki wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 24, 2006, at 4:50 AM, David H. wrote:
Hello fans.
For a long time it has been known that the algorithm we choose your
"closest" mirror by, might not be the best one. Here is a new idea and
I hope you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Community.
I have been thinking about geo-locating Fink Users for quite some time now.
This mainly serves two purposes. First of all I am very curious where all the
people that use Fink actually live and second of all, this should be a service
fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert T Wyatt wrote:
> I think this is a cool idea. Wouldn't it be easier to just set up a
> Frappr page for fink users (http://www.frappr.com/)?
>
One reason would be, that I did not know about this web-site.
The other reason (now that I thought ab
Dear Community
I have carefully reviewed the statistics that we generate for our
Package Database and the recent articles published for our Release of
version 0.8.1
In doing that I have noticed that German spoken countries are the
second largest community using our service, as such I would like t
Dear Community.
Customer Feedback and statements on the quality of a product or
service that come directly from the community are very important for
any company that tries to make money.
They are equally important to us. Your opinion matters, because what
you think of us as a project can very wel
Hello Community.
Popularity is an important factor when it comes to driving an open
source project. Popularity and visitors to an open source project's
home page attract sponsors. Sponsors pay money so that we can ensure
Fink services its community better.
If you have a package in Fink that you m
In reply to my own email :)
>
> Go to the homepage of that package.
> Check whether they provide a link to Fink's homepage. These backlinks
> are very important as search engines calculate our pagerank based on
> that.
> If there is no link, get in touch with the author of the software or
> the we
Dear Community.
Having reviewed our download statistics over the last consecutive
seven days, Fink 0.8.1 has been downloaded once every 60 seconds on
average. That means Fink 0.8,1 has been downloaded over 10.000 times
in just seven days.
Not only should that make us feel good, it shows how loyal
Dear selected community (tricky ehy...)
It know that Fink has had a significant impact on the scientific
community. There are a couple of packages which are in darwinports but
not inf Fink and I would like to get a handle on how popular those
missing packages are in the scientific computing commun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Community.
Before you read this, please make sure you verified and understood that it
comes from a trustworthy source. My name is David Höhn and what I do is
mentioned here on our official web-site:
http://fink.sourceforge.net/people.php?phpLang=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trevor Harmon wrote:
> On Mar 18, 2006, at 8:09 AM, David H. wrote:
>
> I'm not sure why this is necessary. Fink is growing, but that doesn't
> mean it requires a corporate foundation. There are only two reasons
> given on t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Community.
I have to fly to Sydney on business and I would like to meet you. If you are
close to Sydney, or live there, please do not be shy. If you have questions
about fink PR, about the FDN plans or why Benjamin still packages KDE, meet me
:)
Hello.
I just wanted to let you know that I am aware of most of the Problems
that you reported Jesse.
My main concern is to always ensure the availability of the Master
Servers, while the children should be self organised. Much to my
demise I have to admit that I have not put much time lately int
Hello community.
If you know of a hosting service which allows rsync as one of their
hosting services, please let me know. Make sure that you include contact
data and if you know beforehand, what country/state the service would be
hosted in/on.
Thank you very much
-d
>Hi folks:
Hello Bill.
>Periodically, I see posted on other mailing lists or bulletin boards
>a question like "should I use fink or Darwinports or ..."? I'm not
>sure what it says about my state of mind, but I always read these and
>come away somewhat disappointed, because fink often seems
Dear Developers and Users.
In the wake of the ongoing discussion I am going to offer myself as an
archiver.
The Fink Wiki is of course there for everyone to add their ideas and
improvements, but history has shown that human mankind is 'lazy'
I will track the threads and I will try to extract t
>I went to the web site and looked at the packages without .
>aintainers. It was 11 pages long, for a total of 503 packages out of
>6435 listed in my install. That is 7.8%, which on the face of it
>does not seem bad. However, this list is growing fast. The last
>time I looked, the list ha
Dear community.
Reading the Wiki we have some very technical ideas on how to improve
fink. This thread is meant for you and the quirks you have noticed. For
the developers as well as the users.
I will try to track all the feature requests that I might see in this
thread. They will be added to
Dear community.
Reading the Wiki we have some very technical ideas on how to improve
fink. This thread is meant for you and the quirks you have noticed. For
the developers as well as the users.
I will try to track all the feature requests that I might see in this
thread. They will be added to
> I'd like to see a feature that'd slap people for stupidly
> cross-posting...
Dear Timothy,
I am sorry that my cross-posting has offended you. The message was sent
twice on accident. Please also note that I stated quite clearly that
this message has been cross posted. The reason for that is
Cory, Benjamin, go ahead and touch my packages, I do not have time for
that right now.
-d
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opi
Dear Asko.
As someone who watches the legal side of what Fink is doing I can assure
you that we cannot retain any information which would enable us to
identify the user. Legally that would put too many obligations on us and
to have significant statistics that is not necessary. However, assignin
1 - 100 of 115 matches
Mail list logo
