Arne wrote:
Would it be possible to start into that by creating prefixes for the
different package repositories?
(akkuscm ...) and (snow-fort ...)
I advise against doing that, as the same package can be published to
multiple repositories.
Would that be a problem? All it needs is a referenc
Lassi Kortela writes:
>> Would it be possible to start into that by creating prefixes for the
>> different package repositories?
>> (akkuscm ...) and (snow-fort ...)
>
> I advise against doing that, as the same package can be published to
> multiple repositories.
Would that be a problem? All it
Would it be possible to start into that by creating prefixes for the
different package repositories?
(akkuscm ...) and (snow-fort ...)
I advise against doing that, as the same package can be published to
multiple repositories.
(how do I find out whether they are portable? Do I have to try?)
Lassi Kortela writes:
>> Is anything except for (srfi ...) and (rnrs ...) expected to be
>> portable? I thought till now that if I want my code portable, an easy
>> way would be to restrict my imports to these.
>
> The R6RS and R7RS library definition framework (which is broadly
> compatible acro
Is anything except for (srfi ...) and (rnrs ...) expected to be
portable? I thought till now that if I want my code portable, an easy
way would be to restrict my imports to these.
The R6RS and R7RS library definition framework (which is broadly
compatible across both standards) offers a realist
