coin-or
`coinbrew yaml bcp --latest-release` fails
$ coinbrew yaml bcp --latest-release
Welcome to the COIN-OR fetch and build utility, version 2
To use the legacy version of coinbrew, '$ wget https://raw.githubusercontent.com/coin-or/coinbrew/v1.0/coinbrew'
For help, run script with --help or see https://coin-or.github.io/coinbrew
Please report issues at https://github.com/coin-or/coinbrew
Detailed build documentation at https://coin-or.github.io
Fetching latest release 1.4.4
It appears that project has not been fetched yet.
Fetching will be done automatically...
##################################################
### Fetching bcp releases/1.4.4
##################################################
Cloning into 'bcp'...
remote: Enumerating objects: 5424, done.
remote: Counting objects: 100% (6/6), done.
remote: Compressing objects: 100% (6/6), done.
remote: Total 5424 (delta 0), reused 5 (delta 0), pack-reused 5418
Receiving objects: 100% (5424/5424), 4.37 MiB | 10.20 MiB/s, done.
Resolving deltas: 100% (3974/3974), done.
Note: switching to 'cbd92b147af5f7fc44a3e05a89b731f2eb25f715'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
awk: can't open file bcp/.coin-or/projDesc.xml
source line number 1
Yes, this is not going to work. What were you trying to do exactly? The yaml option is an undocumented hack and is basically there temporarily for my own use in converting projects from the old XML-based format to the new YAML format. It shouldn't really be used unless you are trying to help with the conversion effort. If so, I can explain more about how to do this properly.
Just trying to get access to metadata of the packages (including deps), for the purpose of semiautomatically creating packages in the Sage distribution.
Ah, I see. That makes sense. If it's still useful, I can use that as motivation to get to producing the config.yml for some of the projects where it's not done yet. I guess that it shouldn't be too difficult. But if you want to try yourself, it should work running on master. The stable (and hence the latest release) of Bcp doesn't even have a projDesc.xml file and that is what is parsed to get parts of the YAML file that is produced. Just be warned that it doesn't produce anything like valid YAML, it's just a strating point for me to hand-edit.
If it's still useful, I can use that as motivation to get to producing the
config.ymlfor some of the projects where it's not done yet.
Yes, that would be great!