The recent change to support multiple servers broke my own solution to
that problem, which is fine, but the new approach seems odd to me
because it mixes servers and projects by (a) putting the user, password,
and url on a per-project rather than per-server level, and (b) not
accounting for the possibility a project name is re-used on multiple
servers.
If it would help, I can provide an alternative solution that recognizes
a .pwclientrc file with format as below, which meets what I think are
the underlying requirements. This solution would also continue to
recognize the original pwclientrc format, and support the following syntax:
pwclient search cups
pwclient -S ozlabs projects
pwclient query -p meta-freescale
pwclient -S oe2 query -p bitbake
My approach would require somebody to provide new bash_completion
support if that's important, though.
I'm using this internally, and would be happy to prepare a pull request
and discuss how to extend it to other use cases if it's likely to be
acceptable upstream.
Peter
Example new format:
[defaults]
server = oe
[oe]
url = http://patches.openembedded.org/xmlrpc/
default-project = oe-core
username = somename
password = somekey
[oe2]
url = http://patches.openembedded.org/xmlrpc/
default-project = oe
username = othername
password = otherkey
[ozlabs]
url = http://patchwork.ozlabs.org/xmlrpc/
default-project = patchwork
_______________________________________________
Patchwork mailing list
[email protected]
https://lists.ozlabs.org/listinfo/patchwork
