[annotator-dev] Lost in the "current" Annotator 1.2.9 - looking a "state-of-the-art" plugin
Ernesto Torresin (ML)
ewk-ml at connettivo.net
Thu Jun 26 08:12:06 UTC 2014
On 25/06/2014 23:02, Randall Leeds wrote:
> On Wed, Jun 25, 2014 at 3:55 AM, Ernesto Torresin (ML)
> <ewk-ml at connettivo.net <mailto:ewk-ml at connettivo.net>> wrote:
> On 24/06/2014 16:01, Ernesto Torresin (ML) wrote:
> > On 24/06/2014 14:38, Ernesto Torresin (ML) wrote:
> >> On 24/06/2014 13:39, Ernesto Torresin (ML) wrote:
> >>> On 24/06/2014 12:18, Ernesto Torresin (ML) wrote:
> >>>> On 24/06/2014 11:00, Nick Stenning wrote:
> >>> [...]
> >>>> I am using the master branch indeed, because to read the
> sources and
> >>>> compile I was requested by the Makefile to have a .git
> repository. I'm
> >>>> going for the 1.2.x branch now.
> >>> 'npm install .' in the v1.2.x gave me coffescript at 1.6.3 as
> specified in
> >>> package.json and required by coffeebarx at 0.0.3, but Makefile wants to
> >>> call the coffeescript node module with the "--no-header" option,
> >>> was not present in coffeescript before v. 1.7.1 if I understand
> >>> correctly
> >>> Should I modify the package.json or the Makefile?
> >> No way in either way. Requesting a more recent coffeescript module
> >> breaks some dependencies, and removing the "--no-header" option just
> >> lets me hit against sed errors about missing files. BTW I get the
> >> sed errors about missing files if I try to compile the version at
> >> https://github.com/openannotation/annotator/archive/v1.2.9.tar.gz
> >> to at
> >> I am installing npm modules locally in every version, and I can
> >> the clone of the master branch as usual.
> >> Any idea?
> > OK, I don't need minified files to study the code, so I stripped away
> > the pkg/Makefile rules for the min.js files and now the
> > https://github.com/openannotation/annotator/archive/v1.2.9.tar.gz
> > compiles. This sounds like a reasonable start. I'm dropping the v1.2.x
> > branch because I'd like to start with something that was considered
> > stable enough for being released.
> Samll update: to get rid of the fatal git error about
> GIT_DISCOVERY_ACROSS_FILESYSTEM just run make in v1.2.9 as:
> $ export VERSION=1.2.9; make
> Sorry, what fatal error are you talking about?
IIRC if you take
such, do a npm install, and run make, a git "fatal error" shows up. This
1) happens because of the code at tools/preamble
2) is not so "fatal", because compilation goes on
3) was misleading me; it made me git clone the "master" branch, where I
got rid of that error, but I got lost.
More information about the annotator-dev