[gentoo-dev] rfc: pybugz option conflict

[gentoo-dev] rfc: pybugz option conflict

[William Hubbs]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

All,

I have found an option conflict in pybugz, and I would like suggestions
for naming one of the options.

Currently we have two meanings for the --version option.

optparse wants to use --version to display the version of the program,
and we are using --version in the post command to set the version that
will be part of the bug.  What do you think we could use for --version
in the post command instead so that we can use --version to display the
program version?

- -- 
William Hubbs
gentoo accessibility team lead
williamh@gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEARECAAYFAkoIS9QACgkQblQW9DDEZTh8eACfaqCZN3d+SA8JYE8vaCrSy1Y+
S2IAn29zAWDT41DIQtDdkZSngzpEXSmZ
=pwh5
-----END PGP SIGNATURE-----

[gentoo-dev] Re: rfc: pybugz option conflict

[Christian Faulhammer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

William Hubbs <williamh@gentoo.org>:
> optparse wants to use --version to display the version of the program,
> and we are using --version in the post command to set the version that
> will be part of the bug.  What do you think we could use for --version
> in the post command instead so that we can use --version to display
> the program version?

 --bugzilla-version --bugversion

V-Li

- -- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://gentoo.faulhammer.org/>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEARECAAYFAkoIh7wACgkQNQqtfCuFneMpWQCeK0gayJElyJHL4e4WMK6vhhth
a8MAn2wKryzV6wbZNwdYosZX++W/F2ZL
=F7dh
-----END PGP SIGNATURE-----