#333: Supporting local output formats
--------------------------+----------------------
  Reporter:  skaplun      |      Owner:  jcaffaro
      Type:  enhancement  |     Status:  assigned
  Priority:  minor        |  Milestone:  v1.0
 Component:  BibFormat    |    Version:
Resolution:               |   Keywords:
--------------------------+----------------------

Comment (by simko):

 Replying to [comment:4 tbrooks]:
 > 1) The above naming/reinstalling convention causes problems (which for
 the most part can be solved by INSPIRE renaming things correctly)

 Actually the goal of the above conventions is precisely to ease the
 re-installation troubles.  Invenio installations sometimes
 reuse-and-change default demo templates/formats, which is not ideal
 from the upgrade point of view, as we discussed in another ticket
 (ticket:273#comment:3).  We typically advise people to "clone" demo
 files, using their local template skin names.  Having a common
 convention across all modules how to publish `local` changes of this
 kind should make it easier to copy/clone/customise demo configuration
 files even more.

 > 2) [...] CFG_FORMAT_REPO location and when "saving" in the web interface
 it saved bft and bfo files in the repo as well as in the installed code

 For multi-person installations, I'm afraid a simple save to yet
 another place would not work very well, because several people may be
 having access to the BibFormat Admin interface and may be performing
 changes; so copying files to the same non-installation place may
 possibly overwrite each other's work or otherwise create a confusion.
 To solve this, the BibFormat Admin interface would have to behave more
 like an SCM, say use `git push` instead of `cp`.  I'm kind of sceptical
 it would be worth the effort to develop this.

 For single-person installations, this would not be a problem.  But
 then a single person can probably easily make a diff between the
 installation place and his/her source place in order to commit his/her
 changes made via UI.  So dunno if this would be much of an
 improvement?

-- 
Ticket URL: <http://invenio-software.org/ticket/333#comment:5>
Invenio <http://invenio-software.org>

Reply via email to