[asdf-devel] [PATCH 1/2] Fix error in parsing configuration directives
sionescu at cddr.org
Sat Jun 12 18:54:06 UTC 2010
On Mon, 2010-06-07 at 20:47 -0400, Faré wrote:
> It was initially on purpose that I inserted this restriction,
> because I felt that
> 1- there was no clearly good default that I could see.
> 2- if such a default is identified, we can enable it later.
> 3- if no default is initially provided, we can provide one later
> with backwards compatibility; but if we provide one, we can't change
> it with backwards compatibility.
> 4- I'd rather error out early with an annoying error message
> than do something silently that will be the wrong thing for many users.
> Do you really think there should be a default? Which, and for what reason?
> Is there a compelling reason to think that everyone will agree to same
After actually using the configuration system, I came to the conclusion
for the sake of simplicity, ASDF should always inherit configuration,
that :inherit-configuration and :ignore-inherited-configuration should
not exist, and be replaced with a function such as, for example:
asdf:initialize-source-registry-from-defaults &rest conf-sources
by default, upon initialization ASDF would call
(asdf:initialize-source-registry-from-defaults :system :user :env).
Users could override that in the initfiles if needed.
The reason for this is that I want users who install distro-provided
packages to be able to start and use ASDF2 without having to create a
local configuration file.
OTOH, people who don't use distro packages wouldn't care about
inheriting the system configuration because they wouldn't have it, so no
Stelian Ionescu a.k.a. fe[nl]ix
Quidquid latine dictum sit, altum videtur.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part
More information about the asdf-devel