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

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

[Octave-bug-tracker] [bug #56357] pkg: allow more package metadata file


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #56357] pkg: allow more package metadata file names and file extensions
Date: Mon, 20 May 2019 17:19:19 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.131 Safari/537.36

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

                 Summary: pkg: allow more package metadata file names and file
extensions
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Mon 20 May 2019 02:19:17 PM PDT
                Category: Octave Function
                Severity: 1 - Wish
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

The `pkg` command currently requires a package to have a license file named
exactly 'COPYING', which does conform to GNU standards. It also requires the
package news file to be named exactly 'NEWS', if it is present, also
conforming to GNU standards.

Ideally the `pkg` command would be more lenient in what file names it accepts
and interprets for these purposes.

* COPYING - also accept files named COPYRIGHT or LICENSE
* NEWS - also accept files named CHANGELOG, CHANGES, or HISTORY

All of these files names should also be allowed with an optional file
extension of .txt, .md, or .rst.

This would allow package developers to follow other preferences or standards,
and the `pkg` command will still handle and present that information to the
end user.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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