Achim Gratz writes:
> I'll be on it, I should have something to show maybe next weekend.
> Instead of posting a series of patches to the list, I'll add a feature
> branch to my orgmode clone on repo.or.cz — I think that should be easier
> to follow since I expect there will be a few versions back
Achim Gratz writes:
> Yes, but if they've been used, no trace is to be found in the repository
> and in any case, what fixrelease is supposed to be doing is not what it
> actually does — it's currently an exact copy of release. I'll sort it
> out and make a proposal…
Would be nice, thanks.
I ne
Bastien writes:
> this looks like a flexible solution we might use.
Good.
> When you have time, please provide a patch to this effect.
I'll be on it, I should have something to show maybe next weekend.
Instead of posting a series of patches to the list, I'll add a feature
branch to my orgmode c
Bastien writes:
> The targets release and fixrelease are for Org's maintainers.
Yes, but if they've been used, no trace is to be found in the repository
and in any case, what fixrelease is supposed to be doing is not what it
actually does — it's currently an exact copy of release. I'll sort it
ou
Hi Achim,
Achim Gratz writes:
> It looks like the two targets relase and fixrelease have not actually
> been used and at least fixrelease would not do what the comment is
> trying to imply it should be doing. If nobody uses them, these two
> targets should probably be removed.
The targets rele
Hi Achim,
> I went ahead with splitting the Makefile up, it now looks like this:
this looks like a flexible solution we might use.
When you have time, please provide a patch to this effect.
Thanks for you work!
--
Bastien
Achim Gratz writes:
> I just realize that the Makefile already uses several GNU make
> extensions. If it's OK to use them (specifically include files and
> conditional variable assignment), that would help to restructure the
> Makefile so that it can be customized and maintained more easily. Let
I'm on my slackware system right now. Here's the contents of /etc/issue
and I left this as the out of the box default:
Welcome to \s \r (\l)
I had to do git close with the line in the installation notes to get
org-mode to update. The git program refused to overwrite the original
Makefile. So
Achim Gratz writes:
[...]
I just realize that the Makefile already uses several GNU make
extensions. If it's OK to use them (specifically include files and
conditional variable assignment), that would help to restructure the
Makefile so that it can be customized and maintained more easily. Let
Nick Dokos writes:
> My worry is this: before Achim's patch, the "other" systems run the
> following command:
>
> $(INSTALL_INFO) --info-file=$(INFOFILES) --info-dir=$(infodir)
The invocation with --info-files is only understood by GNU install-info,
that was presumably the reason for introd
Bastien wrote:
> Hi Jude,
>
> Jude DaShiell writes:
>
> > The latest patch by Achim Gratz works for this problem for make
> > install-info on debian squeeze. The warning about using ginstall-info
> > comes up, but the documentation updates from 7.5 to 7.6 none the less.
>
> Thanks for conf
Bastien writes:
> Achim and Nick, can I safely apply your patch or was it still a beta
> version?
My patch obsolotes what Nick was trying to achieve, but I'm just looking
at some other stuff in the Makefile that looks like it needs a makeover,
so I'd suggest we discuss this first and I'll submit
Hi Jude,
Jude DaShiell writes:
> The latest patch by Achim Gratz works for this problem for make
> install-info on debian squeeze. The warning about using ginstall-info
> comes up, but the documentation updates from 7.5 to 7.6 none the less.
Thanks for confirming.
Achim and Nick, can I safe
The latest patch by Achim Gratz works for this problem for make
install-info on debian squeeze. The warning about using ginstall-info
comes up, but the documentation updates from 7.5 to 7.6 none the less.
14 matches
Mail list logo
