Re: pkg/39886: GNU emacs and XEmacs modules should not conflict

[David Holland <dholland-pbugs%netbsd.org@localhost>]

The following reply was made to PR pkg/39886; it has been noted by GNATS.

From: David Holland <dholland-pbugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/39886: GNU emacs and XEmacs modules should not conflict
Date: Tue, 13 Dec 2016 19:26:43 +0000

 On Mon, Dec 12, 2016 at 02:55:01PM +0000, Hauke Fath wrote:
  >  >  The offending logic is still there (AFAICT)... however, it seems to me
  >  >  that this should be sorted out as part of a general rehab of emacs
  >  >  modules to support proper multiversion builds. Then one would be able
  >  >  to install the various versions reliably without making a mess.
  >  
  >  I guess the main fault line is between Emacsen and XEmacsen - the 
  >  various Emacsen are much more likely to store things in the same place. 
  >  Looking at emacs/modules.mk, the {x,}e* variables are clearly 
  >  distinguished, paths all different, and there is an xemacs prefix pre-set.
  >  
  >  Wouldn't it be enough to just remove the CONFLICTS settings, then deal 
  >  with the fallout from conflicting PLISTs as it happens?
 
 Probably... go ahead :-)
 
 I think we ought to have proper multiversion builds for elisp packages
 anyway, for various reasons (one being that then the emacs and xemacs
 versions can both be build-tested by pkgbuild) but there's no reason
 that should prevent sorting out things that can be done without it.
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost