Jerker Delsing wrote:
> installed xemacs using fink.
>
> trying to start xemacs gives the following message:
>
> Error: Unresolved inheritance operation
>
> after which xemacs is quitting.
Hard to say anything from this little information. Is there a related
crash log in ~/Library/Logs/CrashRe
On May 10, 2009, at 2:18 PM, Matthew Berginski wrote:
The perltidy package the perl module as well as the stand alone
script, so the entries do appear to cover the same material. I don't
see any reason why they can't be merged and the lines suggested
added to "perltidy.info".
Matt
On Su
I've tried both `fink selfupdate` and `fink selfupdate-cvs` followed
by `fink update-all` to resolve this issue, but it's still here.
+ make
/bin/sh ./libtool --mode=compile cc -c -Os -I../dist/.. ../dist/../
db_dump185/db_dump185.c
cc -c -Os -I../dist/.. ../dist/../db_dump185/db_dump185.c
installed xemacs using fink.
trying to start xemacs gives the following message:
Error: Unresolved inheritance operation
after which xemacs i quitting.
Regards
Jerker
--
Package manager version: 0.27.13
Distribution version: 0.9.0 i386
Mac OS X version: 10.5.6
Xcode version: 3.1.2
gcc version:
The perltidy package the perl module as well as the stand alone script, so
the entries do appear to cover the same material. I don't see any reason why
they can't be merged and the lines suggested added to "perltidy.info".
Matt
On Sun, May 10, 2009 at 9:12 AM, Steve Huff wrote:
> hello folks!
>
On May 10, 2009, at 11:16 AM, David R. Morrison wrote:
>
> On May 10, 2009, at 6:46 AM, Koen van der Drift wrote:
>
>> A package I maintain has some optional components that are downloaded
>> during the install phase inside the expanded tarball. Is this
>> allowed,
>> or should I pre-download e
On May 10, 2009, at 6:46 AM, Koen van der Drift wrote:
> A package I maintain has some optional components that are downloaded
> during the install phase inside the expanded tarball. Is this allowed,
> or should I pre-download everything and then copy it into the expanded
> tarball?
You should p
Hi,
A package I maintain has some optional components that are downloaded
during the install phase inside the expanded tarball. Is this allowed,
or should I pre-download everything and then copy it into the expanded
tarball?
Thanks,
- Koen.
hello folks!
as best i can tell, these two modules are duplicates. if i'm missing
something obvious, please let me know :)
the only package i've found that depends on perl-tidy-pm is perl-
critic-pm*, and i've been able to work around the problem by adding
Provides: perl-tidy-pm
Conflicts
