gopkg.in - Stable APIs for the Go language
Introduction
The gopkg.in service provides versioned URLs that offer the proper metadata for
redirecting the go tool onto well defined GitHub repositories. Developers that
choose to use this service are strongly encouraged to not make any backwards
incompatible changes without also changing the version in the package URL. This
convention improves the chances that dependent code will continue to work while
depended upon packages evolve.
The advantage of using gopkg.in is that the URL is cleaner, shorter, redirects
to the package documentation at godoc.org when opened with a browser, handles
git branches and tags for versioning, and most importantly encourages the
adoption of stable versioned package APIs.
Note that gopkg.in does not hold the package code. Instead, the go tool is
redirected and obtains the code straight from the respective GitHub repository.
The yaml package may be installed by running:
Although a version selector is provided as part of the import path, code
importing it must still refer to the Go package as yaml, its actual name.
Opening that same URL in a browser will present a nice introductory page
containing links to the documentation, source code, and all versions available
for the given package.
The actual implementation of the package is in GitHub:
/go-yaml/yaml
User-owned repositories also work, as described in
GitHub repositories that have no version tags or branches are considered
unstable, and thus in "v0". See the
section below for details.
Supported URLs
There are two URL patterns supported:
gopkg.in/pkg.v3
& /go-pkg/pkg (branch/tag v3, v3.N, or v3.N.M)
gopkg.in/user/pkg.v3 & /user/pkg
(branch/tag v3, v3.N, or v3.N.M)
Path to nested packages may be appended to these URLs.
Version number
The number used in the gopkg.in URL looks like "v1" or "v42", and represents the
major version for the Go package. No incompatible changes should be done to the
package without also changing that version, so that packages and applications
that import the package can continue to work over time without being affected by
broken dependencies.
When using branches or tags to version the GitHub repository, gopkg.in
understands that a selector in the URL such as "v1" may be satisfied by a tag or
branch "v1.2" or "v1.2.1" (vMAJOR[.MINOR[.PATCH]]) in the repository, and will
select the highest version satisfying the requested selector.
Even when using richer versioning schemes, the version selector used in the
gopkg.in URL is restricted to the major version number to ensure that all
packages in a dependency tree that depend on a given versioned URL will pick the
same package version whenever possible, rather than importing slightly different
versions of that package (v1.0.1 and v1.0.2, for example). The only situation
when such duplicated imports may occur is when the package versions are
incompatible (v1 and v3, for example), in which case allowing the independent
imports may provide a chance for the software to still work.
For clarity, assuming a repository containing the following tags or branches:
The following selectors would be resolved as indicated:
pkg.v1 & tag or branch v1
pkg.v2 & tag or branch v2.1.2
pkg.v3 & tag or branch v3.0
Version zero
Version zero (v0) is reserved for packages that are so immature that offering
any kind of API stability guarantees would be unreasonable. This is equivalent
to labeling the package as alpha or beta quality, and as such the use of these
packages as dependencies of stable packages and applications is discouraged.
Packages should not remain in v0 for too long, as the lack of API stability
hinders their adoption, and hurts the stability of packages and applications
that depend on them.
Repositories in GitHub that have no version tag or branch matching the pattern
described above are also considered unstable, and thus gopkg.in takes their
master branch as v0. This should only be used once the package maintainers
encourage the use of gopkg.in, though.
How to change the version
Increasing the version number is done either by registering a new repository in
GitHub with the proper name, or by creating a git tag or branch with the proper
name and pushing it. Which of these are used depends on the choosen convention
section above).
In either case, the previous version should not be removed, so that existent
code that depends on it remains working. This also preserves the documentation
for the previous version at godoc.org.
The GitHub documentation
how to push a tag or branch to a remote.
When to change the version
The major version should be increased whenever the respective package API is
being changed in an incompatible way.
Examples of modifications that DO NEED a major version change are:
Removing or renaming *any* exposed name (function, method, type, etc)
Adding, removing or renaming methods in an interface
Adding a parameter to a function, method, or interface
Changing the type of a parameter or result in a function, method, or interface
Changing the number of results in a function, method, or interface
Some struct changes (see details below)
On the other hand, the following modifications are FINE WITHOUT a major version
Adding exposed names (function, method, type, etc)
Renaming a parameter or result of a function, method, or interface
Some struct changes (see details below)
Note that some of these changes may still break code that depends on details of
the existing API due to the use of reflection. These uses are considered an
exception, and authors of such packages will have to follow the development of
dependend upon packages more closely.
There are also cases that require further consideration. Some of these are
covered below.
Compatibility on struct changes
Adding a field to a struct may be safe or not depending on how the struct was
previously defined.
A struct containing non-exported fields may always receive new exported fields
safely, as the language disallows code outside the package from using literals
of these structs without naming the fields explicitly.
A struct with a significant number of fields is likely safe as well, as it's
inconvenient to be both written and read without naming the fields explicitly.
A struct consisting only of a few exported fields must not have fields added
(exported or not) or repositioned without a major version change, as that will
break code using such structs in literals with positional fields.
Removing or renaming exported fields from an existing struct is of course a
compatibility breaking change.Microsoft - Official Home Page
购买新款 Surface Pro，打造难忘的假期回忆
全球最强大的控制台
让他们体验像素、性能和设计的完美平衡。
物超所值的游戏和娱乐设备。
微软人工智能2.0课程更新版正式开放
无论联机或脱机，均可随时随地访问您的文件。
下载适用于 IT 专业人士的 90 天免费评估版。
预定开发版。改变你的世界。
立即开始构建 Web 应用。
关注更多微软中国市场活动This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use.
CodePlex is going read-only starting November 27th.
This project is read-only.
Are you Sure?
Important Note: This project is no longer supported
There are alternatives and a good whitepaper to read at
Project Description
The Mobile Browser Definition File contains definitions for individual mobile devices and browsers. At run time, ASP.NET uses the information in the request header to determine what type of device/browser has made the request.
This project provides a data file that when used with ASP.NET will detect the incoming mobile device and present you as the web developer with a set of 67 capabilities or properties describing the requesting device. These capabilities range from screen size
to cookie support and provide all the information you need to adaptively render content for mobile phones and devices.
What is the Mobile Device Browser Definition File?
The Mobile Device Browser Definition File contains capability definitions for individual mobile devices and browsers. At run time, ASP.NET uses this .browser file, along with the information in the HTTP request header, to determine what type of device/browser
has made the request and what the capabilities of that device are. This information is exposed to the developer through the
property and allows them to tailor the presentation of their web page to suit the capabilities of the target device.
More Information
The format of the .browser file is XML and the schema is defined here: . The Browser Definition File was introduced in the .NET Framework version 2.0. In earlier versions of the .NET Framework, the
element was used to define browser definitions in configuration files.
Please note that you must have you must have Microsoft .NET Framework 2.0 Service Pack 2 installed to use this .browser file.
Final Release Announcement 15-July-2010
Due to the organizational restructuring of the team that developed and supported the Mobile Device Browser file, we will no longer have the resources to support and update this CodePlex project. The team will be providing two more releases – one on the 27th
July 2010 and the final release on the 24th August 2010.
We would like to thank everyone who used our product over the past year and a half. We would also like to thank everyone who contributed to the discussions and raised issues on our data.
Last edited
by , version 16