Gerald Pfeifer writes:
> On Thu, 20 Apr 2023, Arsen Arsenović wrote:
>>> I understand, just am wondering whether and why the : is required? I
>>> don't think we are using this construct anywhere else?
>> Without them, this would happen:
>>
>> ~$ "${foo:=foo}"
>> bash: foo: command not foun
On Thu, 20 Apr 2023, Arsen Arsenović wrote:
>> I understand, just am wondering whether and why the : is required? I
>> don't think we are using this construct anywhere else?
> Without them, this would happen:
>
> ~$ "${foo:=foo}"
> bash: foo: command not found
> ~ 127 $ unset foo
> ~$ ech
Gerald Pfeifer writes:
> Hi Arsen,
>
> On Fri, 14 Apr 2023, Arsen Arsenović wrote:
>>> Did you intentionally not implement the following part of my suggestion
>>>
>>>if [ x${MAKEINFO}x = xx ]; then
>>>:
>> > that is, allowing to override from the command-line (or crontab)?
>> (answering
Hi Arsen,
On Fri, 14 Apr 2023, Arsen Arsenović wrote:
>> Did you intentionally not implement the following part of my suggestion
>>
>>if [ x${MAKEINFO}x = xx ]; then
>>:
> > that is, allowing to override from the command-line (or crontab)?
> (answering both the questions)
>
> This := oper
Gerald Pfeifer writes:
> On Tue, 11 Apr 2023, Arsen Arsenović wrote:
>> Ah! Good idea. What do you think of the following?
>
> Did you intentionally not implement the following part of my suggestion
>
>if [ x${MAKEINFO}x = xx ]; then
>:
>
> that is, allowing to override from the comman
On Tue, 11 Apr 2023, Arsen Arsenović wrote:
> Ah! Good idea. What do you think of the following?
Did you intentionally not implement the following part of my suggestion
if [ x${MAKEINFO}x = xx ]; then
:
that is, allowing to override from the command-line (or crontab)?
And why the colon
Gerald Pfeifer writes:
> On Thu, 6 Apr 2023, Arsen Arsenović wrote:
>> maintainer-scripts/ChangeLog:
>>
>> * update_web_docs_git: Add updated Texinfo to PATH
>
> Do we really need to adjust PATH, or could we just introduce a MAKEINFO
> variable, something like
>
> if [ x${MAKEINFO}x = x
On Thu, 6 Apr 2023, Arsen Arsenović wrote:
> I must ask that whoever decides to apply/update the script tests
> texi2any with a simple example, like
>
> echo @node Top | ~/texinfo/install-git/bin/makeinfo --html -o -
>
> ... before updating; this should be a representative enough smoke test.
>
On Thu, 6 Apr 2023, Arsen Arsenović wrote:
> maintainer-scripts/ChangeLog:
>
> * update_web_docs_git: Add updated Texinfo to PATH
Do we really need to adjust PATH, or could we just introduce a MAKEINFO
variable, something like
if [ x${MAKEINFO}x = xx ]; then
if [ -x /home/gccadmin/t
maintainer-scripts/ChangeLog:
* update_web_docs_git: Add updated Texinfo to PATH
---
Hi,
I'm posting this as a ping and a patch necessary to get the wwwdocs
building with the new Texinfo version that's installed on gcc.gnu.org.
It would be nice to do this ahead of the GCC 13 release.
I m
10 matches
Mail list logo
