bug#50728: closed (Update Pandoc (just on my machine))

[GNU bug Tracking System]

Your message dated Thu, 23 Sep 2021 08:57:19 -0400
with message-id <87v92rjvps.fsf@gmail.com>
and subject line Re: bug#50728: Update Pandoc (just on my machine)
has caused the debbugs.gnu.org bug report #50728,
regarding Update Pandoc (just on my machine)
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
50728: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=50728
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Update Pandoc (just on my machine)
>
>
>
>
> Date: 
>
> Tue, 21 Sep 2021 16:46:05 -0700
>
>
>
>
> I know that there is this issue:
>
> http://issues.guix.gnu.org/39798
>
> And it was closed because Guix wants to stay with the LTS version of
> Haskell.
>
> But I need to use some features that come in later versions of pandoc.
>
> A few of my static site generator projects break because I need features
> that come after 2.7.x, which is the version that Guix packages.
>
> Can someone explain to me how to package the latest pandoc just on my
> own computer?
>
> Thanks.
>
> ~vidak
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#50728: Update Pandoc (just on my machine)
>
>
>
>
> Date: 
>
> Thu, 23 Sep 2021 08:57:19 -0400
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
>
>
>
>
> Hello,
>
> vidak@riseup.net writes:
>
> > I know that there is this issue:
> >
> > http://issues.guix.gnu.org/39798
> >
> > And it was closed because Guix wants to stay with the LTS version of
> > Haskell.
> >
> > But I need to use some features that come in later versions of pandoc.
> >
> > A few of my static site generator projects break because I need features
> > that come after 2.7.x, which is the version that Guix packages.
> >
> > Can someone explain to me how to package the latest pandoc just on my
> > own computer?
> >
> > Thanks.
>
> The first step is configuring a development setup as explained in "info
> '(guix)Contributing" sections.
>
> Then you'd want to update the version and source fields with the new
> version details (guix hash -rx on the checkout or guix download
> https://tarball-url) to retrieve the new hash.
>
> Then you'd summarily review the new sources for important changes such
> as a change to their licensing.  A Changelog or NEWS file can be helpful
> to understand what has changed, if available.
>
> Then you'd start iterating on building the new package with something
> like:
>
> $ ./pre-inst-env guix build pandoc
>
> If it's your lucky day it'll build without any change; but if it's a
> major update you might have to modify the inputs or even update them in
> prior commits.
>
> Good luck!
>
> If you have further questions, please ask on the help-guix@gnu.org
> mailing list.  I'll close this bug, as this tracker should remain focus
> on actual bugs rather than update/packaging requests.
>
> Thanks,
>
> Maxim
>
>
> --- End Message ---