Is there a policy about what encoding to use for .info files? The fink
tool (or specifically perl 5.8.x) and online package database seem to
expect Unicode while FinkCommander assumes MacRoman. There are two
files, gtktalog.info and recode.info, that use MacRoman in the
Maintainer field. Thus t
Robert Wyatt wrote:
Howdy,
I updated my 10.2-gcc3.3 to 0.24.0 today and something didn't work out
quite right. How do I proceed with this one?
[]
Failed: Can't use an undefined value as filehandle reference at
/sw/lib/perl5/Fink/Package.pm line 360.
Do you have UseBinaryDist: true in your /sw/etc
Dear Fink developers,
I wrote some guidelines that should help FOSS projects getting more lively and
lowering the barrier for new developers to join. You can find them in form of a
small manual here
http://projects.mi.fu-berlin.de/w/bin/view/SE/ThesisFOSSIMMediationManual.
These ideas are the
In fink-0.23.5-1, when the gcc3.1.pkg was not installed and a package
was to be built that had a BuildDepends: gcc3.1, one got the short and
unclear, but clearly visible error message
Failed: Can't resolve dependency "gcc3.1" for package "prcs-1.3.2-1" (no matching packages/versions found)
and t
Martin,
Yes, I have UseBinaryDist: true in fink.conf.
I changed the line in question per your instructions below, and
everything is copacetic.
Thanks! --robert
At 10:21 AM +0100 2/25/05, Martin Costabel wrote:
Robert Wyatt wrote:
Do you have UseBinaryDist: true in your /sw/etc/fink.conf? If yes,
Daniel Johnson wrote:
I couldn't find anything in the Packaging Manual about this. Perhaps a
good policy would be to require all .info files to use UTF-8 and
document this?
I would vote for 7-bit ASCII, if possible. Everything else gives
trouble. Just look at the package database and try to find
On Fri, Feb 25, 2005 at 10:21:46AM +0100, Martin Costabel wrote:
> Robert Wyatt wrote:
> >Howdy,
> >
> >I updated my 10.2-gcc3.3 to 0.24.0 today and something didn't work out
> >quite right. How do I proceed with this one?
> []
> >Failed: Can't use an undefined value as filehandle reference at
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Johnson wrote:
|
| I couldn't find anything in the Packaging Manual about this. Perhaps a
| good policy would be to require all .info files to use UTF-8 and
| document this?
|
As far as I am aware, any package not using plain old ascii is in viol
On Fri, Feb 25, 2005 at 11:38:53AM +0100, Martin Costabel wrote:
> In fink-0.23.5-1, when the gcc3.1.pkg was not installed and a package
> was to be built that had a BuildDepends: gcc3.1, one got the short and
> unclear, but clearly visible error message
>
> >Failed: Can't resolve dependency "gc
On Fri, Feb 25, 2005 at 08:33:04AM -0500, Daniel Johnson wrote:
> Is there a policy about what encoding to use for .info files?
They are supposed to be "plain text files" in the traditional Unix
sense. As such, I don't think there's is any issue about encoding.
The validator emits a warning if a .
Daniel Macks wrote:
Sure 'nuf! Does:
open APTDUMP, "$basepath/bin/apt-cache dump |"
function correctly? That's the canonical form we use elsewhere.
Yes, it does work.
---
SF email is sponsored by - The IT Product Guide
Read honest & candid r
Daniel Macks wrote:
[]
Failed: Can't resolve dependency "gcc3.1" for package "prcs-1.3.2-1" (no
matching packages/versions found)
and the build process stopped right there before it even started.
...and then the user is completely stuck, as we well know from reading
the lists.
But this message c
Daniel Macks <[EMAIL PROTECTED]> wrote:
> Update of /cvsroot/fink/fink/perlmod/Fink
> In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29536
>
> Modified Files:
> Package.pm ChangeLog
> Log Message:
> perl-5.6 compatibiility fix for open() syntax.
>
I'm thinking of back-porting this
On Feb 25, 2005, at 10:24 AM, Daniel Macks wrote:
open APTDUMP, "$basepath/bin/apt-cache dump |"
Perl usually discourages this form, since if someone could convince
$basepath to bstart with ">" it might do bad things.
Why not stick with this?
open APTDUMP, "-|", "$basepath/bin/apt-cache dump
I think good.
---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.
On 25-Feb-05, at 1:00 PM, David R. Morrison wrote:
Daniel Macks <[EMAIL PROTECTED]> wrote:
Update of /cvsroot/fink/fink/perlmod/Fink
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29536
M
TheSin wrote:
> I think good.
yeah, but wait for me to check in some changes to make virtual failures
a bit more verbose.
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real user
I think it needs tweaking:
bash-2.05b$ fink selfupdate
syntax error at /sw/lib/perl5/Fink/Package.pm line 361, near "or"
Compilation failed in require at /sw/lib/perl5/Fink/Engine.pm line 34.
BEGIN failed--compilation aborted at /sw/lib/perl5/Fink/Engine.pm line 34.
Compilation failed in require at
can't have that first ;
---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.
On 25-Feb-05, at 1:39 PM, Robert T Wyatt wrote:
I think it needs tweaking:
bash-2.05b$ fink selfupdate
syntax error at /sw/lib/perl5/Fink/Package.pm line 361, near "or"
Compilation fai
open APTDUMP, "$basepath/bin/apt-cache dump |"
or die "Can't run apt-cache dump: $!";
this works, sorry, must have had a typo.
Robert T Wyatt wrote:
I think it needs tweaking:
bash-2.05b$ fink selfupdate
syntax error at /sw/lib/perl5/Fink/Package.pm line 361, near "or"
Compilati
On Fri, Feb 25, 2005 at 03:00:54PM -0500, David R. Morrison wrote:
> Daniel Macks <[EMAIL PROTECTED]> wrote:
>
> > Update of /cvsroot/fink/fink/perlmod/Fink
> > In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29536
> >
> > Modified Files:
> > Package.pm ChangeLog
> > Log Message:
> > p
On Fri, Feb 25, 2005 at 03:12:11PM -0500, Dave Vasilevsky wrote:
>
> On Feb 25, 2005, at 10:24 AM, Daniel Macks wrote:
> > open APTDUMP, "$basepath/bin/apt-cache dump |"
>
> Perl usually discourages this form, since if someone could convince
> $basepath to bstart with ">" it might do bad thi
On Feb 25, 2005, at 10:15 AM, Daniel Macks wrote:
On Fri, Feb 25, 2005 at 08:33:04AM -0500, Daniel Johnson wrote:
Is there a policy about what encoding to use for .info files?
They are supposed to be "plain text files" in the traditional Unix
sense. As such, I don't think there's is any issue about
22 matches
Mail list logo
