I have submitted the revised source code (i.e., winexe ported to current samba git "master" branch) to winexe's author but it is not yet clear to me what he plans to do with it.
The winexe build needs access to the samba source tree. This has not changed in my port. I have looked into the possibility of building winexe against Samba 4 *-dev packages. Unfortunately, the latter do not include all the needed header files. One possible course of action would be to work with the Samba 4 maintainers to get the missing header files included in the -dev files. But there are quite a few header files missing, so I wouldn't expect this request to be met with much enthusiasm. Given that winexe has to be built against the samba source tree, I think it's best if we try to get winexe included in Samba 4. If this attempt fails then winexe will have to be maintained separately from Samba. Winexe upstream will have to be maintained as a Samba 4 fork. The pain of this can be minimized by syncing regularly with Samba 4 master. For Debian we can then revisit the idea of building against -dev packages by including more headers. -- Thomas -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/cajn8kfc8mdignw8y7+x38kuq6bmhrazr1je2wq8fzx0vkgg...@mail.gmail.com
