New subpackage xfig-Xaw3d

Hans de Goede j.w.r.degoede at hhs.nl
Sat Nov 17 10:37:37 UTC 2007


Jonathan Underwood wrote:
> On 17/11/2007, Patrice Dumas <pertusus at free.fr> wrote:
>> On Sat, Nov 17, 2007 at 10:50:05AM +0100, Joachim Frieben wrote:
>>> As of build #24591, the "xfig" package has been split up into "xfig-common", a plain "xfig" package built against the "Xaw" widget library and a new "xfig-Xaw3d" package which is built against the "Xaw3d" widget set.
>>> Many other distros moved to using "Xaw3d" in the past, and it's good news to have this in "Fedora" now, too. However, it appears suboptimal to me that there now exist 2 packages which provide the same functionality only differing by the underlying widget library. I'd prefer dropping "xfig-Xaw3d" and "xfig" being built by default against "Xaw3d" which is already required by the new "xdvi" package of "tetex" successor "texlive" scheduled for inclusion into the next release. This would avoid clutter and unnecessary confusion.
>> This kind of choice is best left to the package maintainer.
>>
> 
> IMO It would be better if the xfig package was the one built against
> Xaw3D, and there was an optional xfig-Xaw package though, for the
> older widget kit.

That can be done. As of recently I'm a co-maintainer of xfig, and I'm the one 
who introduced the xfig-Xaw3d package, all 3 options:
-Xaw3d only build
-both, Xaw3d the default
-both, Xaw the default

Are fine with me, I did things as they are now as xfig had a lot of bugs open 
against them, so the latest release, besides adding an Xaw3d package also fixes 
a lot of bugs, thus its being pushed as an update for F-7 and F-8 too. And I 
didn't want this update to cause a widget set change, going from the principle 
of least surprise. But I can easily switch the default to Xaw3d for rawhide if 
people prefer that, or even make the rawhide package an Xaw3d only build.

Regards,

Hans




More information about the devel mailing list