SourceForge has been redesigned. Learn more.
Close

#1901 mingw-get: use consistent naming of packages

INSTALLER
open
None
Feature
none
Unknown
False
2013-02-15
2011-05-17
khagaroth
No

Please use identical names for packages and their corresponding catalog files. Most packages follow this rule, but some use different names and it's a pain to have to open the catalog file and look for the correct name inside and mingw-get list is too verbose to be usable.
A few examples:
GCC4 - mingw32-gcc4.xml - mingw32-gcc
MinGW runtime - mingw32-runtime.xml - mingw32-mingwrt
etc.

Discussion

  • khagaroth

    khagaroth - 2011-05-17
    • summary: mingw-get: use consistent naming of components --> mingw-get: use consistent naming of packages
     
  • Keith Marshall

    Keith Marshall - 2011-05-19

    Thanks for this suggestion.

    > Please use identical names for packages
    > and their corresponding catalog files

    Unfortunately, this isn't really practical.

    First, there isn't a one-to-one correspondence between packages and catalogues -- the mingw32-runtime.xml catalogue encapsulates both the mingwrt package, (as you've identified), AND the w32api package, (which you've overlooked). There are several package collections which are encapsulated in this manner.

    Second, the distribution of the catalogue across multiple files isn't a mingw-get requirement -- indeed mingw-get reads a specified list of input files which it immediately consolidates into a single internal catalogue; at no time thereafter does it care that this catalogue was sourced from multiple files. The segregation into separate files is purely a convenience for package maintainers, and IMO it is important that they be left free to exploit the feature as it best fits their individual package maintenance needs.

    I'm sorry that you find `mingw-get list' to be too verbose. mingw-get-0.3 will add features to allow more selective output choices. In the meantime, you can always redirect and filter the verbose output, to extract what is useful to you, (as I did for the mingw-get-info script I posted a month or so ago).

    Beyond my planned enhancements to output choices for 'mingw-get list' (and 'mingw-get show'), I don't see any practical advantage in pursuing this. I will, however, consider any suggestions you may like to make, regarding report formats you would find useful for 'mingw-get list' options.

     
  • Keith Marshall

    Keith Marshall - 2011-05-19
    • status: open --> pending
     
  • khagaroth

    khagaroth - 2011-05-19

    I guess, that ideal would be to have 'list' for showing a list of available packages and their components only (without any description and using a more condensed format than the current, preferably one line per component) and 'show' for showing extended information about a concrete package.

     
  • Keith Marshall

    Keith Marshall - 2011-05-19

    The 'list' and 'show' functions are handled by the same piece of code. I'd always planned that their output styles could be controlled by user specified options, with different default sets for each. Your request is consistent with my own planned objective, but before we can get to that, the mechanism for handling options needs to be in place. I'm currently working out the protocol for that, as a prerequisite to the imminent first-cut mingw-get-0.3 release.

    I'll leave this open for now, with low priority. We can revisit, and perhaps escalate, when I get to implementation of list/show options.

     
  • Keith Marshall

    Keith Marshall - 2011-05-19
    • priority: 5 --> 1
    • assigned_to: nobody --> keithmarshall
    • status: pending --> open
     
  • Robert Hartmann

    Robert Hartmann - 2011-09-23

    Hi keithmarshall,
    You said: "[...] I will, however, consider any suggestions you may like to make, regarding
    report formats you would find useful for 'mingw-get list' options."

    I think it would be nice to get a list from installed packages.

    mingw-get list installed
    => a pure list of package names are installed (it is usefull to check if two ore more installations on differend machines are equal or to check what is missing to be equal with some other installation!)

    mingw-get list
    => a pure list of package names with information of dependencies

    mingw-get list <packagename>
    => lists all packages which one must have installed so that <packagename> can be used.

    mingw-get show
    => same user interface but verbose information i.e. content description.

     
  • Earnie Boyd

    Earnie Boyd - 2013-02-15

    Ticket moved from /p/mingw/feature-requests/90/

     
  • Earnie Boyd

    Earnie Boyd - 2013-02-15
    • labels: Suggested Feature -->
    • milestone: Submitted --> INSTALLER
    • type: --> Feature
    • resolution: --> none
    • category: --> Unknown
    • patch_attached: --> False
     

Log in to post a comment.