[asdf-devel] Last call before code freeze

[Faré]

>>: rpg
>: dherring

>> It's not a blocker to not have good system-dependencies, as Daniel says.
>>  But given that, I think the blocker is that we should rip out the
>> system-dependencies misfeature.  It's not right yet, so we shouldn't
>> ship it, and encourage people to use it.
>
> Would it be possible to document this as an experimental feature?  Say its
> busted, give an example why, and encourage people to suggest improvements?
>  Insert a style-warning that triggers when people use it?
>
> Trying to avoid code changes right before a release,
>
Yes, I'm wary of having to change code, then change it back, especially
considering how painful it is to get all the bugs out every time.

Moreover, I'll argue that it's not the system-dependencies feature being
deficient here, but the version feature being deficient. system-depends-on
works fine, and does the job.

Finally, this feature is already undocumented and therefore experimental.
However, it works in the simple cases, and I don't see why not encourage
its use, especially since ASDF now allows better control of which version
of ASDF itself you use, and hence detection of version mismatches.

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
"I wish there was a knob on the TV to turn up the intelligence.
There's a knob called `brightness', but it doesn't work."
		— Gallagher