Omar Polo writes:

> Omar Polo <o...@omarpolo.com> writes:
>
>> Björn Gohla <b.go...@gmx.de> writes:
>>
>>> Hi All,
>>>
>>> Is there any particular reason why we don't have a Guile 3
>>> (https://www.gnu.org/software/guile/) port?
>>>
>>> (I might secretly try making one.)
>>
>> I tried some time ago, because I was curious about the language.  You
>> can find attached my attempt: I'm not familiar with the guile ports, and
>> definitely not familiar with the language (i played only a little with
>> it) but maybe it can saves you some time.  (I just copied the guile2 and
>> changed the version number and the package name).
>>
>> Surprisingly, it passes port-lib-depends-check and portcheck O.O
>>
>> Cheers,
>>
>> Omar Polo
>
> mail sent too fast.  The tarball included also some CVS directories,
> here's the cleaned up version.  Sorry for the noise

Nice. Thanks. I was able to build the package. The only problem
seems to be that the names of the info manual files overlap with those
of guile2, i.e., I get this when I try to install:

titanic# TRUSTED_PKG_PATH=/usr/ports/packages/amd64/all/ pkg_add guile3
Collision in guile3-3.0.4: the following files already exist
        /usr/local/info/guile.info (guile2-2.2.7 and guile3-3.0.4)
        /usr/local/info/guile.info-1 (guile2-2.2.7 and guile3-3.0.4)
        /usr/local/info/guile.info-10 (guile2-2.2.7 and guile3-3.0.4)
        /usr/local/info/guile.info-2 (guile2-2.2.7 and guile3-3.0.4)
        /usr/local/info/guile.info-3 (guile2-2.2.7 and guile3-3.0.4)
        /usr/local/info/guile.info-4 (guile2-2.2.7 and guile3-3.0.4)
        /usr/local/info/guile.info-5 (guile2-2.2.7 and guile3-3.0.4)
        /usr/local/info/guile.info-6 (guile2-2.2.7 and guile3-3.0.4)
        /usr/local/info/guile.info-7 (guile2-2.2.7 and guile3-3.0.4)
        /usr/local/info/guile.info-8 (guile2-2.2.7 and guile3-3.0.4)
        /usr/local/info/guile.info-9 (guile2-2.2.7 and guile3-3.0.4)
        /usr/local/info/r5rs.info (guile2-2.2.7 and guile3-3.0.4)
Couldn't install guile3-3.0.4

Is there a recommended way for solving this conflict? (Other than
disabling the info docs entirely.) 

--
Cheers,
Björn

Reply via email to