On Mar 23, 2012, Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx> wrote:
> Hi P.,
> On Thursday, 22. March 2012 22:02:07 P. Martin wrote:
> > Hello, I admit to knowing little about VCS, but I'm having a problem with
> > libftdi-0.20 where it tries to install to lib64 on OSX when using CMake.
> > Your git repo shows that this was patched in December in:
> > 08dc0034ded8494844bc489871ae9a21f93e8635
> > Your 0.20 commit is after that in January, but if I follow the parent
> > commits backwards, it skips around to September. Is that expected?
> > The result is that I can't really package this for Homebrew correctly.
> > Ok, thanks.
> We currently have two active "branches" of libftdi:
> libftdi 1.x "master" and the legacy, supported branch "libftdi-0.x".
> The commit you mentioned is only part of the "master" branch.
> Easiest thing for your packaging is to extract the single change on the
> "master" branch and apply it to the libfdtdi 0.20 tarball during packaging.
Ahh, I didn't notice the two branches. Now I see what's happened.
Thank you for explaining that. In the case where a fix that exists in
head won't be backported to stable, the Homebrew maintainers
will wait for a new version that does work.
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx