octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #57522] "pkg unload" does not care for depende


From: Rik
Subject: [Octave-bug-tracker] [bug #57522] "pkg unload" does not care for dependencies
Date: Mon, 3 Feb 2020 12:48:12 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko

Update of bug #57522 (project octave):

                  Status:         Patch Submitted => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #31:

I pushed the change to use "any (idx)" here:
https://hg.savannah.gnu.org/hgweb/octave/rev/f6f9341c46c1.

Turns out there were still stray debug comments ("# keyboard") left in the
code.  That was probably my fault so I removed that here:
https://hg.savannah.gnu.org/hgweb/octave/rev/a6d57446cdb3.

I made some slight modifications to the NEWS file addition and checked it in
here (https://hg.savannah.gnu.org/hgweb/octave/rev/cc0b31003932).  Biggest
change was that NEWS now uses Markdown and the delimiter for code segments is
the backtick (`) rather than the apostrophe (').  I also wrapped long lines to
72 characters since we have decided on that for the NEWS file in particular,
and used two spaces after a period and before the first word of a new
sentence.

The last issue, changing pkg to be potentially case insensitive, needs to be
decided first at a strategic level.  Is this something we want?  Coders from
UNIX-based OS'es would generally say "No".  Coders from MS-based OS'es would
generally say "Yes".  If a decision is arrived at then it should be
implemented in a single changeset across all the relevant files making up pkg
behavior, rather than one changeset at a time.  That is why I decided to use
strcmp rather than strcmpi for the time being. 

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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