On Sat, Jul 21, 2001 at 06:40:52PM +0200, Asger K. Alstrup Nielsen wrote:
> Integrating all of this, maybe this hybrid solution would work:
>
> Provide a dialog which lists all the packages that the document
> potentially need. For each package, the dialog will say which section
> of CTAN the package is in (base, supported, contrib, unknown), preferably
> with a full path, and also a short description.
> For each package, the user will have the option to choose between
> "use package" which will use the package unconditionally,
> "use best available" which will use the fallback method as
> url.sty, and "do not use package". The default should be the
> fallback method, since that's a good choice for most.
>
> Now, to make it easy to adjust to a certain group, the dialog could
> provide shortcuts similar to your compatibility options. So, with
> one operation, all packages could be restricted to the ones in
> base and supported.
In some sense, this is even worse: it requires a lot of code for a rather
useless feature.
