09 Mar, 2015

1 commit


06 Mar, 2015

1 commit

  • $ rake -f Rakefile.translations
    
    The above invocation will work without a full rails environment, which
    requires a config/database.yml, an actual database to connect to, plus
    loading all the Rails stack which is painfully slow.
    
    This can now be used by distribution packages to compile translations
    during package build without worrying much.
    Antonio Terceiro
     

25 Feb, 2015

2 commits


24 Feb, 2015

1 commit


22 Feb, 2015

1 commit


07 Feb, 2015

1 commit


28 Jan, 2015

2 commits


15 Jan, 2015

2 commits


14 Jan, 2015

1 commit


22 Dec, 2014

1 commit


15 Dec, 2014

1 commit


12 Dec, 2014

1 commit


09 Dec, 2014

1 commit


08 Dec, 2014

1 commit


04 Dec, 2014

1 commit


27 Nov, 2014

1 commit


24 Nov, 2014

1 commit


19 Nov, 2014

1 commit


13 Nov, 2014

2 commits


07 Nov, 2014

2 commits


05 Nov, 2014

1 commit


01 Nov, 2014

1 commit


31 Oct, 2014

1 commit


29 Oct, 2014

2 commits


28 Oct, 2014

1 commit


27 Oct, 2014

2 commits


12 Sep, 2014

5 commits


09 Sep, 2014

1 commit


20 Aug, 2014

1 commit

  • When a system that has plugin X enabled gets upgraded to a version where
    plugin X has been promoted to be a base plugins (i.e. a symlink in
    baseplugins/), `rake db:migrate` would blow up with
    
      Multiple migrations have the version number 12345678901234
    
    Note that we probably don't need to do this deduplication everywhere
    else, because the Ruby $LOAD_PATH already works by giving prioriry to
    the first path that is found.
    Antonio Terceiro