Summary: | xemacs-21.1.14 package also broken (gnus failure in 21.4.6 and sandbox problem for 21.1.14) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matthew Kennedy (RETIRED) <mkennedy> |
Component: | New packages | Assignee: | Matthew Kennedy (RETIRED) <mkennedy> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | agenkin, golpa |
Priority: | High | ||
Version: | 1.0 RC6 r14 | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://lists.gentoo.org/pipermail/gentoo-user/2002-April/021602.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Matthew Kennedy (RETIRED)
2002-04-24 01:48:10 UTC
As far as MULE support goes, I'd suggest either having "mule" as a USE option, or creating separate ebuilds (i.e. xemacs-mule). The latter is a cleaner way, IMO. Arcady, I agree. BTW, I have some plans for app-editors/xemacs. Something like this: xemacs (the stable branch) xemacs-gamma xemacs-beta and possibly, xemacs-mule (the stable branch) xemacs-mule-gamma xemacs-mule-beta Each xemacs except for stable can handle either GTK+ or motif interfaces. Since motif and gtk can both be USE flags, I'll need some way to determine the user's preference in the case they have BOTH gtk and motif in USE. I haven't resolved this aspect yet. The reason for providing stable, gamma and beta, is that each are quite usable and stable (I've been using GTK+ gamma heavily for over a year). The ~/.xemacs layout is distinctly different for gamma and beta though. I'll scrub up this proposal and mail it to gentoo-core for a bit of peer review... hopefully this weekend. Note, because we'd multiply out the number of xemacs ebuilds to maintain to three by providing stable, gamma and beta... we'll probably want to avoid multiplying out to six by providing additional -mule versions. In this case it might be better to not have -mule versions, and just keep the mule USE check within. Especially: if I cannot find a way to check for a gtk/motif preference within an ebuild, I'll need: xemacs-gtk-gamma xemacs-gtk-beta in addition anyway. Matt Don't forget the regular (Lucid) version. ;^) You ideas sound fine. My main concern was not to include MULE support for everyone. okay, what i've settled on is this: add a mule and lucid USE flag. add xemacs-gamma and xemacs-beta to app-editors/ since there's no way to determine a preference on a subset of USE yet, if the user has gtk, motif and lucid set (or some combination of that), then build xemacs binaries for each. eg. USE="lucid motif ...", then: /usr/bin/xemacs-21.4.6-motif /usr/bin/xemacs-21.4.6-ludic /usr/bin/xemacs -> xemacs-21.4.6-motif and have some kind of util ala. opengl-update/java-config -style to switch between them. (really just a symlink rename). We'll also check for mule as a USE flag. I've got most of this done. need to add some stuff and test more though. app-editors/xemacs-gamma/xemacs-21.4.7.ebuild will be released shortly. it will fix this and other problems (ie. add optional mule support, lucid, motif, gtk too) matt |