>>>> "ville" == Ville Skytt <Ville>
writes:
ville> Another idea; when package A does not _require_ package B, but having B
ville> around would bring in some extra goodies to A's functionality; a
ville> RECOMMENDS feature could help. Again, maybe versioned as said above.
ville> There's already some discussion about this in [3]. Oh, and then a
ville> (versioned?) CONFLICTS relation between packages that don't coexist
ville> nicely...
Up to here sounds good. However, CONFLICTS is tricky. What one would
desire is for CONFLICT to prevent or warn about packages being
required w/o others being unloaded, or some to that effect, since
different peopls could want different sets of packages (or same user,
at different times under different tasks).
best,
-tony
--
A.J. Rossini Rsrch. Asst. Prof. of Biostatistics
U. of Washington Biostatistics rossini(a)u.washington.edu
FHCRC/SCHARP/HIV Vaccine Trials Net rossini(a)scharp.org
--------------
http://software.biostat.washington.edu/ ----------------
FHCRC: M-W: 206-667-7025 (fax=4812)|Voicemail is pretty sketchy/use Email
UW: Th: 206-543-1044 (fax=3286)|Change last 4 digits of phone to FAX
(my friday location is usually completely unpredictable.)