Hannes Hauswedell
Hannes Hauswedell
We are currently working on 2.0.1 and also performing some infrastructural changes (moving the apps out of the repo...). The 2.1.0 milestone is still valid and I am afraid this...
@marehr Please don't just abandon issues without discussion. In this case it can just be closed, or not?
Hm, I have looked at the Debian scripts, and it seems you are doing most of the actual packaging manually by copying the files and doing sed on some of...
But can't you make two successive builds? Or even two independent ones? I mean, I have no strong feelings either way, I just thought it could reduce the maintenance overhead....
> @h-2 Not really. Could we have another SEQAN_BUILD_SYSTEM that does it all? We have the `DEVELOP` target that builds everything, but it doesn't install :disappointed: I would prefer not...
> I think this issue can be closed: Cool, thanks!
Actually, no. The cmake file is still: `/usr/share/cmake/seqan-config.cmake` As noted in my initial post, this directory is not searched.
Now you are installing two: ``` /usr/share/cmake/seqan-config.cmake /usr/share/cmake/seqan/seqan-config.cmake ``` Is that intentional?
@mr-c Is the double config install fixed? Can I close this issue? Thanks!
@xenigmax what is the status here?