Edgewall Software

Changes between Version 16 and Version 17 of MultipleRepositorySupport


Ignore:
Timestamp:
Feb 2, 2009, 2:45:58 PM (13 years ago)
Author:
Christian Boos
Comment:

various updates to reflect the current state of affairs

Legend:

Unmodified
Added
Removed
Modified
  • MultipleRepositorySupport

    v16 v17  
    1212 - r6465: initial "release" of the branch, ''worksforme''
    1313 - r6469: a few bug fixes
    14  - r7590: current version is quite good ;-)
     14 - r7590: that version was quite good
     15 - r7815: current version is still quite good ;-)
    1516
    1617The approach is quite simple: beyond repository connectors, there's now repository providers (IRepositoryProvider components) which are responsible for make available a list of named repositories. That name can be arbitrary (in particular, it may contain '/' to denote a pseudo-hierarchy) and will be used as a prefix for any repository path.
     
    8788}}}
    8889   - !SvnParentDirRepositoryProvider, for listing all the Subversion repositories present in a given folder
    89  - currently, a "default" repository (the one defined in the `[trac]` section) ''needs'' to be defined, otherwise the versioncontrol modules are disabled
     90 - currently, a "default" repository (the one defined in the `[trac]` section) ''needs'' to be defined, otherwise the versioncontrol modules are disabled [[span(class=important,FIXME)]]
    9091 - ~~fix AJAX query in annotate~~
    91  - IRepositoryProvider must have a way to signal new content, in order to rebuild the repository name cache
     92 - IRepositoryProvider must have a way to signal new content, in order to rebuild the repository name cache - `trac-admin ... repository changeset`, see #7723.
    9293 - support the `.url` repository metadata (#1781)
    93  - small issue: visual glitch in Firefox 2 for the new Rev column,
     94 - ~~ small issue: visual glitch in Firefox 2 for the new Rev column,
    9495   where the changeset icon doesn't align properly to the right
    95    (but works fine for every other web browser, including Firefox 3)
     96   (but works fine for every other web browser, including Firefox 3) ~~ FF 2 is now dead, isn't it?
    9697 - "normal" feature: it's currently not possible to compare across repositories
    9798   (the situation is detected, but raises a "not implemented" error).
    9899   It would be quite useful to be able to do so, and it's doable without much work
    99100   (only need to compare folders in a backend neutral way, we already do our own diff at the file level)
    100  - extend to '''cached repositories''', see MultipleRepositorySupport/Cache. [[br]]
     101 - extend to '''cached repositories''', see MultipleRepositorySupport/Cache and #7723 [[br]]
    101102   In a first step, the existing cache could be adapted to simply handle more than one repository. [[br]]
    102103   Bonus points if that cache is smart enough to handle multiple scoped repositories without data duplication. [[br]]
     
    110111> 1. How can I get the name in the ''Repository Index'' to keep the case in the name? It is converted to lower case.
    111112
    112 ConfigParser limitation.
     113!ConfigParser limitation (#7378).
    113114
    114115> 2. Since you use the init tag as the name to show in the ''Repository Index'', it seems I cannot have a period in the name of the repository as shown.
     
    118119> 3. I get a ''default'' in the ''Repository Index'', as well as that same repository listed in the previous single repository manner. I think that when the multiple repositories are listed, and one of them is the same as the trac repository_dir, it does not need to be listed twice or three times.
    119120
    120 Yes, known issue, currently it's not possible to get rid of the "default" repository, specified in `[trac]` (see [#TODO]). What you suggest is that aliases (even aliases for the `[trac] repository_dir`) shouldn't be listed, I think that's acceptable, but there should be an easy way to learn about the defined aliases, maybe they can be listed at the bottom of the toplevel page.
     121Yes, known issue, currently it's not possible to get rid of the "default" repository, specified in `[trac]` (see [#TODO]).
     122 - one possibility would be to not list aliases (even aliases for the `[trac] repository_dir`). I think that's acceptable, but there should be an easy way to learn about the defined aliases, maybe they can be listed at the bottom of the toplevel page.
     123 - OTOH, aliases might be defined simply because they are more convenient names than the "real" ones, so in the end, more flexibility is needed. Add a `.browseable` flag, a la Samba?
    121124
    122125> Other than that, so far this is going to meet my needs quite nicely. Thanks!