Bug 1153751 - Review Request: golang-github-spf13-pflag - Drop-in replacement for Go's flag package, implementing POSIX/GNU-style --flags
Summary: Review Request: golang-github-spf13-pflag - Drop-in replacement for Go's flag...
Keywords:
Status: CLOSED DUPLICATE of bug 1085890
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-16 17:30 UTC by Jan Chaloupka
Modified: 2014-10-16 18:30 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-16 18:30:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jan Chaloupka 2014-10-16 17:30:54 UTC
Spec URL: https://jchaloup.fedorapeople.org/reviews/golang-github-spf13-pflag/golang-github-spf13-pflag.spec

SRPM URL: https://jchaloup.fedorapeople.org/reviews/golang-github-spf13-pflag/golang-github-spf13-pflag-0-0.1.git463bdc8.fc20.src.rpm

Description: pflag is a drop-in replacement for Go's flag package,
implementing POSIX/GNU-style --flags.

pflag is compatible with the GNU extensions to the POSIX recommendations
for command-line options. For a more precise description,
see the "Command-line flag syntax" section below.

pflag is available under the same style of BSD license as the Go language,
which can be found in the LICENSE file.

Fedora Account System Username: jchaloup

Koji: http://koji.fedoraproject.org/koji/taskinfo?taskID=7884479

$ rpmlint /home/jchaloup/rpmbuild/RPMS/noarch/golang-github-spf13-pflag-devel-0-0.1.git463bdc8.fc20.noarch.rpm /home/jchaloup/rpmbuild/SRPMS/golang-github-spf13-pflag-0-0.1.git463bdc8.fc20.src.rpm golang-github-spf13-pflag.spec
2 packages and 1 specfiles checked; 0 errors, 0 warnings.

Comment 1 Jan Chaloupka 2014-10-16 18:30:43 UTC

*** This bug has been marked as a duplicate of bug 1085890 ***


Note You need to log in before you can comment on or make changes to this bug.