On Tue, Apr 05, 2016 at 09:29:59PM +0100, Stuart Henderson wrote:
> On 2016/04/05 21:15, Juan Francisco Cantero Hurtado wrote:
> > On Tue, Apr 05, 2016 at 06:42:06PM +0100, Stuart Henderson wrote:
> > > On 2016/04/05 00:51, Juan Francisco Cantero Hurtado wrote:
> > > > >
> > > > > Here is the whole go update as a single huge diff including lang/go,
> > > > > devel/go-tools, three new go ports, websocketd update and
> > > > > net/websocketd
> > > > > removal. The changes to juanfra@'s lang/go diff boil down to
> > > > > simplified
> > > > > install stage - I copy over everything and then remove bootstrap.
> > > > >
> > > > > I considered removing tests, but upstream says that go implementation
> > > > > should serve a reference for good practices in go development, so
> > > > > these
> > > > > tests may serve a reference implementation purposes.
> > > > >
> > > > > OK?
> > > >
> > > > Sorry for the delay.
> > > >
> > > > - Use "@comment" for the bootstrap lines in PLIST
> > >
> > > It's easier to handle updates if you rm rather than @comment.
> > > But let's hear what the maintainer says first :-)
> >
> > Why is easier? update-plist would keep the lines with @comment, right?
>
> Yes and that is part of the problem, it will keep *all* the lines with
> @comment (even if some of the files are removed), but it won't add any
> new @comment markers for files in the same directory.
>
> For the same reason it's usually better to rm *.la rather than add them
> as @comments.
Forget about my comment. I didn't see the line "rm -R
${GOROOT}/pkg/bootstrap" in the Makefile. The files will not show up
again in the future in the PLIST.
--
Juan Francisco Cantero Hurtado http://juanfra.info
