[Bug 189197] Review Request: ghc-gtk2hs

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: ghc-gtk2hs


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189197





------- Additional Comments From gemi at bluewin.ch  2006-05-01 12:07 EST -------
(In reply to comment #5)
> Yes, guess you're right.  (It seems to be the default place gtk2hs installs
> the docs, though personally I quite like it since I have it bookmarked and
> it is nice not to have to update it every time the version is incremented.

I completely agree! However versioning the doc directories is the
convention, and unfortunately this convention will hardly change.

> > 9. Currently, if someones builds a package requiring the gconf part
> >    of gtk2hs, he will need to require ghc642-gconf, even if he doesn't
> >    care about the exact version of ghc. Requiring ghc-gtk2hs does the
> >    right thing, but only for gtk, glib and cairo. Would
> >    "Provides: ghc-gconf" etc... work?
> 
> Well that works, but then the problem is that ghc642-gconf will conflict with
> ghc641-gconf, etc.  An alternative might be to make ghc-gtk2hs pull in all the
> subpackages perhaps?
Wouldn't that defeat the purpose of splitting off these packages?

I wonder if this versioning scheme is really worth the effort. After all
there are no shared libraries, where compatibility packages would be
necessary. Of course everytime ghc gets updated, the dependent packages
must be rebuilt...

I am currently building the package in mock...

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.