[Bug 3538] New: extension interdependencies

[bugzilla-daemon at bz.selenic.com]

http://bz.selenic.com/show_bug.cgi?id=3538

          Priority: normal
            Bug ID: 3538
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: extension interdependencies
          Severity: feature
    Classification: Unclassified
                OS: Linux
          Reporter: sphink at gmail.com
          Hardware: PC
            Status: UNCONFIRMED
           Version: unspecified
         Component: Mercurial
           Product: Mercurial

Quite a few extensions have dependencies on each other, and it seems like
there's no good way to express those dependencies. Examples: mq adds the --mq
option to other extensions' commands, color/pager/etc want to colorize other
extensions' output.

I have an extension that layers on top of mq. In order to be independent of the
order in which the extensions are listed in .hgrc, I wrapped mq.uisetup to
force it to be called first and then call my setup routine. It's complex and
fragile, and sure enough it broke in a recent version when mq switched over to
extsetup instead.

Rather than relying on a never-ending arms race, I'd really like to just say
'depends on mq'. Or, more specifically, that my extension (mqext,
https://bitbucket.org/sfink/mqext) wants to add arguments to mq commands, so
they need to exist before my setup routine is run. I don't know what
granularity would be best to expose, but it's very possible that you'd want
portions of an extension's setup to interleave differently.

-- 
You are receiving this mail because:
You are on the CC list for the bug.