Re: Pandoc Tool
Keith F Prussing <[email protected]>
| Newsgroups | gmane.comp.programming.tools.scons.user |
|---|---|
| Message-ID | <[email protected]> |
And [PR] submitted. I'm just glad to help! I decided to forgo transferring the entire history because it was quite a bit of a mess. Instead, I opted to just link to the original history for archival purposes. While cleaning up to contribute I did come up with a couple questions: 1. I managed to figure out how to get `pip install` working with a directory structure similar to scons-contrib. However, it does install directly to the SCons directory in the installation and appears to only work with SCons >4. Is the scons-contrib project interested in getting that up and running? 2. Have you thought about adopting a pattern like [sphinx-contrib]? If SCons knew to check the `sconscontrib.<package>` that could lower the barrier to Tool contribution. But that would obviously be a fundamental change within SCons itself. If either of these is more appropriate over on the dev list, I'm happy to migrate the discussion over there. Keith [PR]: https://github.com/SCons/scons-contrib/pull/37 [sphinx-contrib]: https://github.com/sphinx-contrib/ On 2021-07-01, Bill Deegan wrote: >Also if you can MIT license the code that make's it possible for us to pull >into core at some point if that makes sense. > >On Thu, Jul 1, 2021 at 9:54 AM Mats Wichmann <[email protected]> wrote: > >> >> On 7/1/21 7:09 AM, Bill Deegan wrote: >> > Keith, >> > That'd be great! >> > >> > Let us know if you need any help. >> > >> > -Bill >> > SCons Project Co-Manager >> > >> > On Thu, Jul 1, 2021 at 12:17 AM Keith Prussing <[email protected] >> > <mailto:[email protected]>> wrote: >> > >> > Over the past few years I've been poking at a [Tool] for SCons to >> > add support for Pandoc by scanning dependencies including images, >> > filters, templates, and bibliographies. I think I finally have it >> > stable enough for general perusal. If there is enough interest, I'd >> > be willing to contribute it to the [scons-contrib] repository to >> > make it easier for others to locate and use it. >> > >> > [Tool]: https://github.com/kprussing/scons-pandoc >> > <https://github.com/kprussing/scons-pandoc> >> > [scons-contrib]: https://github.com/SCons/scons-contrib >> > <https://github.com/SCons/scons-contrib> >> >> For grins, I used this recipe to prepare a PR pulling another externally >> developed tool into scons-contrib while keeping its history, if that's >> something you want to do (that PR remains outstanding so you won't see >> the result in the existing scons-contrib git) >> >> # inside my scons-contrib working tree... >> git remote add -f sconscontrib/SCons/Tool/qt4 >> [email protected]:dirkbaechle/scons_qt4.git >> git merge --strategy=ours --no-commit --allow-unrelated-histories >> sconscontrib/SCons/Tool/qt4/master >> git read-tree --prefix=sconscontrib/SCons/Tool/qt4 -u >> sconscontrib/SCons/Tool/qt4/master >> git commit -m "subtree merged in sconscontrib/SCons/Tool/qt4" >> >> >> >> https://github.com/SCons/scons-contrib/pull/36 >> _______________________________________________ >> Scons-users mailing list >> [email protected] >> https://pairlist4.pair.net/mailman/listinfo/scons-users >> >_______________________________________________ >Scons-users mailing list >[email protected] >https://pairlist4.pair.net/mailman/listinfo/scons-users -- Keith F Prussing