On 21 August 2017 at 14:11, Michael Hudson-Doyle
<michael.hud...@canonical.com> wrote:
> On 22 August 2017 at 01:17, Paul R. Tagliamonte <paul...@gmail.com> wrote:
>> Why not use the import path I so lovingly put in the generated control
>> file for times like these?
> That's still missing from heaps of packages, isn't it? I know someone who
> likes writing scripts to fix lots of golang packages at once...

Also, some packages include multiple import paths, usually via a
symlink.  These are often the result of a rename, or of two imports
for the same project (ala, "github.com/foo/bar" and
"gopkg.in/foo/bar.vN"), so it might be worth considering making that a
list instead of simply a single package path.

- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Pkg-go-maintainers mailing list

Reply via email to