org manual not updating when pulling from git

org manual not updating when pulling from git

[Charles Millar]

When pulling from git, shouldn't the manual be updated if for no other 
reason than to refelct the most recent org version?

Up unitl two or three days ago, this was my experience. Now, however, 
none of the documentation seems to be updating, e g.

current Org mode version 9.0.4 (release_9.0.4-283-g2064b0 @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)

pdf manual shows version Release 9.0.4 (release 9.0.4-263-gf15728)

As far as I know I have not changed any settings on my end.

Charlie MIllar

Re: org manual not updating when pulling from git

[Nick Dokos]

Charles Millar <millarc@verizon.net> writes:

> When pulling from git, shouldn't the manual be updated if for no other
> reason than to refelct the most recent org version?
>

It depends on what you mean by "the manual" - the texinfo source is updated,
but any derived files (info, pdf) are not: they are not under source control
at all.

> Up unitl two or three days ago, this was my experience. Now, however,
> none of the documentation seems to be updating, e g.
>
> current Org mode version 9.0.4 (release_9.0.4-283-g2064b0 @
> /usr/local/share/emacs/site-lisp/org-mode/lisp/)
>
> pdf manual shows version Release 9.0.4 (release 9.0.4-263-gf15728)
>

"make doc" or "make pdf" will update the PDF file. If you use one of
the update targets in the makefile, it may have been updating the pdf
doc under the covers. Taking a look through recent commits, the only one
that might be relevant seems to be this:

,----
| commit c90c7a33f53ad88dfcc583ad4c77bec306da0b22
| Author: Marco Wahl <marcowahlsoft@gmail.com>
| Date:   Wed Feb 1 11:16:16 2017 +0100
| 
|     targets.mk: Drop the rule to clean at every compile
|     
|     Rationale: 1. Save time and energy.  2. Use the make tool for what
|     it's been made.
`----

So, how do you update?

-- 
Nick

Re: org manual not updating when pulling from git

[Achim Gratz]

Nick Dokos writes:
> "make doc" or "make pdf" will update the PDF file. If you use one of
> the update targets in the makefile, it may have been updating the pdf
> doc under the covers. Taking a look through recent commits, the only one
> that might be relevant seems to be this:
>
> ,----
> | commit c90c7a33f53ad88dfcc583ad4c77bec306da0b22
> | Author: Marco Wahl <marcowahlsoft@gmail.com>
> | Date:   Wed Feb 1 11:16:16 2017 +0100
> | 
> |     targets.mk: Drop the rule to clean at every compile
> |     
> |     Rationale: 1. Save time and energy.  2. Use the make tool for what
> |     it's been made.
> `----

That commit should probably be reverted.  The make tool can't do what
it's been made for in this case since some of the dependencies can not
be correctly determined.  You can still skip the clean if you want to by
using the compile-dirty target.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

Re: org manual not updating when pulling from git

[Marco Wahl]

Hi!

Achim Gratz <Stromeko@nexgo.de> writes:

> Nick Dokos writes:
>> "make doc" or "make pdf" will update the PDF file. If you use one of
>> the update targets in the makefile, it may have been updating the pdf
>> doc under the covers. Taking a look through recent commits, the only one
>> that might be relevant seems to be this:
>>
>> ,----
>> | commit c90c7a33f53ad88dfcc583ad4c77bec306da0b22
>> | Author: Marco Wahl <marcowahlsoft@gmail.com>
>> | Date:   Wed Feb 1 11:16:16 2017 +0100
>> |
>> |     targets.mk: Drop the rule to clean at every compile
>> |
>> |     Rationale: 1. Save time and energy.  2. Use the make tool for what
>> |     it's been made.
>> `----
>
> That commit should probably be reverted.  The make tool can't do what
> it's been made for in this case since some of the dependencies can not
> be correctly determined.  You can still skip the clean if you want to by
> using the compile-dirty target.

Ah!  I didn't see target 'compile-dirty'.  Thank you for the hint.

So for now I'm happy with the build process with the existence of

    make compile-dirty

and further

    make test-dirty

Also the names are well chosen AFAICT.

I agree that the commit should be reverted and I already did the revert.
Please accept my apology for the irritation about the build behavior.


Best regards

                       Marco
                       

Re: org manual not updating when pulling from git

[Charles Millar]

Hi,


On 02/07/2017 02:41 PM, Nick Dokos wrote:
> Charles Millar <millarc@verizon.net> writes:
>
>> When pulling from git, shouldn't the manual be updated if for no other
>> reason than to refelct the most recent org version?
>>
> It depends on what you mean by "the manual" - the texinfo source is updated,
> but any derived files (info, pdf) are not: they are not under source control
> at all.
>
>> Up unitl two or three days ago, this was my experience. Now, however,
>> none of the documentation seems to be updating, e g.
>>
>> current Org mode version 9.0.4 (release_9.0.4-283-g2064b0 @
>> /usr/local/share/emacs/site-lisp/org-mode/lisp/)
>>
>> pdf manual shows version Release 9.0.4 (release 9.0.4-263-gf15728)
>>
> "make doc" or "make pdf" will update the PDF file. If you use one of
> the update targets in the makefile, it may have been updating the pdf
> doc under the covers. Taking a look through recent commits, the only one
> that might be relevant seems to be this:
>
> ,----
> | commit c90c7a33f53ad88dfcc583ad4c77bec306da0b22
> | Author: Marco Wahl <marcowahlsoft@gmail.com>
> | Date:   Wed Feb 1 11:16:16 2017 +0100
> |
> |     targets.mk: Drop the rule to clean at every compile
> |
> |     Rationale: 1. Save time and energy.  2. Use the make tool for what
> |     it's been made.
> `----
>
> So, how do you update?
>
I forgot about make doc; in the past I used it whenever I had to 
recompile org from source; after that the pdf "just updated" each time I 
pulled from git.

Charlie

Re: org manual not updating when pulling from git

[Nick Dokos]

Charles Millar <millarc@verizon.net> writes:

>> So, how do you update?
>>
> I forgot about make doc; in the past I used it whenever I had to
> recompile org from source; after that the pdf "just updated" each time
> I pulled from git.
>

The question was: *how* do you pull from git? If you use one of the make
targets (e.g. make update), that's one thing; but if you use "git pull" or
some variant thereof that does *not* involve make, then the pdf would *not*
"just update" (unless you've set up some git hook to do some post-processing).

-- 
Nick

Re: org manual not updating when pulling from git

[Charles Millar]

On 02/08/2017 11:39 AM, Nick Dokos wrote:
> Charles Millar <millarc@verizon.net> writes:
>
>>> So, how do you update?
>>>
>> I forgot about make doc; in the past I used it whenever I had to
>> recompile org from source; after that the pdf "just updated" each time
>> I pulled from git.
>>
> The question was: *how* do you pull from git? If you use one of the make
> targets (e.g. make update), that's one thing; but if you use "git pull" or
> some variant thereof that does *not* involve make, then the pdf would *not*
> "just update" (unless you've set up some git hook to do some post-processing).
>
I use make update. Now it is "working" as before.

Charlie

Re: org manual not updating when pulling from git

[Marco Wahl]

Charles Millar <millarc@verizon.net> writes:
> I use make update. Now it is "working" as before.

Good!  This indicates that the revert of the commit in question has been
applied.

This is the commit message:

#v+
     Revert commit c90c7a33f53ad88dfcc583ad4c77bec306da0b22

     targets.mk: Revert to cleanup at every compile for 'standard' targets.

     Note: You can do 'dirty' builds with 'make compile-dirty' and 'make
     test-dirty'.
     - Disadvantage: these builds may fail due to the missing clean.
     - Advantage: typically the 'dirty' builds are much faster.
#v-


Best regards

                       Marco

Re: org manual not updating when pulling from git

[Achim Gratz]

Marco Wahl writes:
> Ah!  I didn't see target 'compile-dirty'.  Thank you for the hint.
>
> So for now I'm happy with the build process with the existence of
>
>     make compile-dirty
>
> and further
>
>     make test-dirty
>
> Also the names are well chosen AFAICT.
>
> I agree that the commit should be reverted and I already did the revert.
> Please accept my apology for the irritation about the build behavior.

No problem.  But in the future, please ask here first if you think you
find something in the build system that you can optimize.  Maybe it was
an oversight or it's a workaround that has become obsolete, but usually
there's an actual reason behind.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada