[Mono-devel-list] Re: Potential GAC implementation ideas.

[Todd Berman]

> There are pre- and post-scripts for both installation and removal inside
> of RPM.  The problem with the post-install script, however, is that the
> files are changed on the filesystem by the time the scripts are run, so
> if the script fails, the entire transaction isn't rolled back.  This
> means a potential inconsistent state if that script fails.  Using the
> force flag to RPM doesn't have any effect on that, and in fact almost
> always makes things worse.

By force, I meant the gacutil force install flag :)

> The advantage to just having mono pick them up automatically (a
> conf.d-like setup) is that there's no intervention required; once you've
> fixed the GAC they Just Work.  But the disadvantage then is that the
> layout and implementation of the GAC become public and basically a part
> of the mono ABI.

Again, my main issue with the conf.d type setup is two-fold:

1) Cache for a cache?!?
2) Multiple versions of the same library (part of the reason the GAC exists)


--Todd