I think I understand the problem, but I'm not sure I understand the
solution (I'm probably missing something). :-)
* Regarding the usability problem mentioned, I still don't see how a
user could easily see all the dependencies of an egg if the egg file
has only `(auto-dependencies)'.
* Reg
> > Actually, perhaps the best way would be to use a custom build
> > using csm to build the components of the egg. A little bit of
> > inventiveness might be required, but I think it should be possible.
>
> This would make the egg depend on csm. I don't mind this for programs,
> but for eggs that
On Mon, 21 Nov 2022 19:09:43 +0200 Lassi Kortela wrote:
>> My take on that as a user: I care about dependencies and tend to avoid
>> eggs with many dependencies. If I see `(auto-dependencies)' in an egg
>> file, I don't know the dependencies of that egg. I would not like that.
>> Also, that wou
> > Actually, perhaps the best way would be to use a custom build
> > using csm to build the components of the egg. A little bit of
> > inventiveness might be required, but I think it should be possible.
>
> This would make the egg depend on csm. I don't mind this for programs,
> but for eggs that
Actually, perhaps the best way would be to use a custom build
using csm to build the components of the egg. A little bit of
inventiveness might be required, but I think it should be possible.
This would make the egg depend on csm. I don't mind this for programs,
but for eggs that are just libra
Actually, perhaps the best way would be to use a custom build
using csm to build the components of the egg. A little bit of
inventiveness might be required, but I think it should be possible.
I added a "-compile-imports" to csm today to force import libs to
be compiled, which may be a start. Perha
My take on that as a user: I care about dependencies and tend to avoid
eggs with many dependencies. If I see `(auto-dependencies)' in an egg
file, I don't know the dependencies of that egg. I would not like that.
Also, that would break the [reverse] dependency ranks of salmonella
reports.
aut
On Mon, 21 Nov 2022 17:58:27 +0100 Mario Domenech Goulart
wrote:
> On Sun, 20 Nov 2022 20:55:09 +0200 Lassi Kortela wrote:
>
>> I have a .egg file for a portable Scheme program substantial enough
>> and fast-moving enough that the dependencies are constantly getting
>> out of sync.
>>
>> Would
Hi Lassi,
On Sun, 20 Nov 2022 20:55:09 +0200 Lassi Kortela wrote:
> I have a .egg file for a portable Scheme program substantial enough
> and fast-moving enough that the dependencies are constantly getting
> out of sync.
>
> Would it be possible to add a feature something like this?
>
> (extensi
It's ambiguous. There can be (and are) eggs that export procedures of the same name.
Procedures are exported from modules, not from eggs, right? Where's the
conflict?
Dependencies shouldn't get out of sync, and updated versions may change what is
exported... so I would question exactly what
> Would it be possible to add a feature something like this?
>
> (extension foo.bar
>(source "bar.sld")
>(auto-dependencies) ; <-- The new feature.
>(csc-options "-R" "r7rs" "-X" "r7rs"))
>
> auto-dependencies would compute the deps by traversing the given source
> file. It would look
It's ambiguous. There can be (and are) eggs that export procedures of the same
name.
Dependencies shouldn't get out of sync, and updated versions may change what is
exported... so I would question exactly what you are doing that would require
such functionality and whether there would be a bet
I have a .egg file for a portable Scheme program substantial enough and
fast-moving enough that the dependencies are constantly getting out of sync.
Would it be possible to add a feature something like this?
(extension foo.bar
(source "bar.sld")
(auto-dependencies) ; <-- The new feature.
13 matches
Mail list logo