Stephen J. Turnbull wrote:
Mike Kupfer writes:
> When I (someday) get the mh-e package updated, I'll be wanting to change
> package-compile.el to reflect moving the sources from mh-e/ to
> mh-e/lisp/. I suppose that changes like this won't happen very often,
> so they can be managed by submitting patches to Norbert (or whoever is
> the package builder). Does this sound okay?
IMHO, that's the way it has to be until Norbert (or successor) says
In the long run, we probably *can* go to a standard "DAGgy" workflow
for reviewers who conform to the procedures Norbert establishes for
himself, and then Norbert just does a merge as necessary. But for
now, Norbert doesn't yet have a firm grasp on the mechanics of
subrepos (and I certainly don't) -- let's not give him any puzzles to
solve that we don't need to. (He can always play sudoku if he wants
That all sounds fine to me. (I don't have a firm grasp of subrepos,
The other thing I was thinking of was possibly refactoring some of the
build infrastructure, so that changes like reorganizing a package's
source files could be done without touching any of the top-level files.
I'm not sure it's worth the effort, and it's not something I could look
into any time in the forseeable future. But if it sounds like that
might be useful, I could create a wishlist item for it in the tracker.
XEmacs-Beta mailing list