[Scons-users] Pandoc Tool
Keith F Prussing
kprussing74 at gmail.com
Sat Jul 3 00:50:10 EDT 2021
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.
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 <mats at wichmann.us> 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 <kprussing74 at gmail.com
>> > <mailto:kprussing74 at gmail.com>> 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
>> git at github.com:dirkbaechle/scons_qt4.git
>> git merge --strategy=ours --no-commit --allow-unrelated-histories
>> git read-tree --prefix=sconscontrib/SCons/Tool/qt4 -u
>> git commit -m "subtree merged in sconscontrib/SCons/Tool/qt4"
>> Scons-users mailing list
>> Scons-users at scons.org
>Scons-users mailing list
>Scons-users at scons.org
Keith F Prussing
More information about the Scons-users