bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #65800] bootstrap oddity: .gitignore discrepancy


From: Dave
Subject: [bug #65800] bootstrap oddity: .gitignore discrepancy
Date: Mon, 27 May 2024 20:54:09 -0400 (EDT)

URL:
  <https://savannah.gnu.org/bugs/?65800>

                 Summary: bootstrap oddity: .gitignore discrepancy
                   Group: GNU roff
               Submitter: barx
               Submitted: Mon 27 May 2024 07:54:09 PM CDT
                Category: Core
                Severity: 2 - Minor
              Item Group: Build/Installation
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Mon 27 May 2024 07:54:09 PM CDT By: Dave <barx>
I haven't built a groff since 1.23.  When I did so recently
(http://lists.gnu.org/r/groff/2024-05/msg00042.html), the first step produced
a query I hadn't seen in a groff build before.

$ ./bootstrap
/bin/mv: overwrite '.gitignore'?

I said "y" to this, and the result was that the top-level .gitignore file
gained a "/build-aux" line at the top, before the first comment.  The line
"/build-aux/" (with the trailing slash), already in the file in the "artifacts
expected in a clean tree" section, remained unaltered, so "/build-aux" now
appears twice, once with the trailing slash and once without.

This has no effect I could discern on the rest of the bootstrap or build.  I
don't know whether it constitutes a bug, but it seems weird for the bootstrap
script to require user input to continue, especially devoid of any context
about the significance of the decision, or even which of the tree's many
.gitignore files it refers to.







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65800>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]