[emacs-w3m:13199] Re: [emacs-w3m/emacs-w3m] bb_travis - add different versions and operating systems and pictures! (#16)

> The first problem of this PR is that the travis recipe does not install FLIM packge, thus it is impossible to detect byte-compile errors of shimbun modules.

My first guess is that the way to handle that is to add to the travis `before_script` section, a batch invocation of emacs to perform something like:
```
     (package-list-packages)
     (package-install "flim")
```
Should `apel` and any other packages also be installed?

> The second problem which is shared by the original travis recipe is that docker container migration is recommended by Travis.

Yes! I knew about that, but didn't fin the documentation, and since the documentation for the other method was so prominent, I went that route. But, you are right.

> I think the first problem is merge blocker of this PR, and the second problem is optional.

There will probably be other hiccups as well. For instance, I don't have a clear idea what version of the build tools are being used, and haven't gotten travis to display stdout when I included `foo --version` in the build script.

Also, I see that it seems osx does not install `w3m` by default, so that needs to be done explicitly by travis.

The nature of this work may mean many small experimental commits, so I took to being liberal, and then at the end performing a wholesale 'squash' using `git rebase`. It went smoothly, and is why there was originally only a single commit to this PR.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/emacs-w3m/emacs-w3m/pull/16#issuecomment-465130215