Re: installing the Newt

[todd mitton]

I should have said that new users will be able to 'go get
mynewt.apache.org/newt/...' once Chris's changes have been merged onto
master.

On Thu, Mar 3, 2016 at 10:53 AM, todd mitton  wrote:

> Sorry.  I was waiting to switch to the vanity import domain until all the
> other rename changes were done.  I didn't realize we were ready.
>
> New users can now do this:
>
> go get mynewt.apache.org/newt/newt
> go get mynewt.apache.org/newt/newtmgr
> go get mynewt.apache.org/newt/newtvm
>
> The user won't need to manually clone the repo.  go get will clone it into
> $GOPATH/src/mynewt.apache.org/newt.  By default the user will be on the
> master branch. If the user wishes to be on develop, they can:
>
> cd $GOPATH/src/mynewt.apache.org/newt
> git checkout develop
>
> -Todd
>
> On Wed, Mar 2, 2016 at 11:46 PM, Christopher Collins 
> wrote:
>
>> I have committed the changes to the develop branch.  Now all go imports
>> use the vanity domain.
>>
>> Unfortunately, this is going cause a bit of pain for the current users
>> because the newt sources are now in the wrong directory.  To correct
>> this problem, you will need to move the old newt path to the new one:
>>
>> $ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
>>   mv $GOPATH/src/
>> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt "$GOPATH"/src/
>> mynewt.apache.org/newt
>>
>> If you plan on building older versions of newt, you should link the path
>> rather than move it:
>>
>> $ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
>>   ln -s $GOPATH/src/
>> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt "$GOPATH"/src/
>> mynewt.apache.org/newt
>>
>> Sorry for the hassle.  Yes, we definitely need to include convenience
>> binaries in the next release :).
>>
>> Chris
>>
>> On Wed, Mar 02, 2016 at 11:21:49PM -0800, Christopher Collins wrote:
>> > Nice!  That seems to work.  I guess I completely glossed over those
>> > vanity URL emails.  I will make the necessary changes to the develop
>> > branch.  Unfortunately, I'm afraid it is too late to fix 0.8.0-b1.
>> >
>> > Chris
>> >
>> > On Wed, Mar 02, 2016 at 10:40:53PM -0800, Sterling Hughes wrote:
>> > >
>> > > >
>> > > > When pointed at the apache server, on the other hand, "go get"
>> seems to
>> > > > require the ".git" suffix.  An I mentioned earlier, this results in
>> the
>> > > > creation of a directory that also has the ".git" suffix.
>> > > >
>> > > > The problem is: the behavior of "git clone" is in conflict with the
>> > > > behavior of "go get", at least with regards to the apache git
>> server.
>> > > > At one point the installation documentation was accurate, but it
>> seems
>> > > > we have since opted for git-friendliness rather than
>> > > > go-get-friendliness.
>> > > >
>> > > > We will need to find a simpler workaround.  In the meantime, we
>> should
>> > > > at least update the documentation.  Also, soon newt binaries will be
>> > > > available for download which help to alleviate problems with go.
>> > > >
>> > >
>> > > Weren't Todd & Aditi making "mynewt.apache.org" a valid import path,
>> > > that would point to the proper Apache git repository?   I thought this
>> > > would solve that problem?
>> > >
>> > > Sterling
>>
>
>

Re: installing the Newt

[todd mitton]

Sorry.  I was waiting to switch to the vanity import domain until all the
other rename changes were done.  I didn't realize we were ready.

New users can now do this:

go get mynewt.apache.org/newt/newt
go get mynewt.apache.org/newt/newtmgr
go get mynewt.apache.org/newt/newtvm

The user won't need to manually clone the repo.  go get will clone it into
$GOPATH/src/mynewt.apache.org/newt.  By default the user will be on the
master branch. If the user wishes to be on develop, they can:

cd $GOPATH/src/mynewt.apache.org/newt
git checkout develop

-Todd

On Wed, Mar 2, 2016 at 11:46 PM, Christopher Collins 
wrote:

> I have committed the changes to the develop branch.  Now all go imports
> use the vanity domain.
>
> Unfortunately, this is going cause a bit of pain for the current users
> because the newt sources are now in the wrong directory.  To correct
> this problem, you will need to move the old newt path to the new one:
>
> $ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
>   mv $GOPATH/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt
> "$GOPATH"/src/mynewt.apache.org/newt
>
> If you plan on building older versions of newt, you should link the path
> rather than move it:
>
> $ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
>   ln -s $GOPATH/src/
> git-wip-us.apache.org/repos/asf/incubator-mynewt-newt "$GOPATH"/src/
> mynewt.apache.org/newt
>
> Sorry for the hassle.  Yes, we definitely need to include convenience
> binaries in the next release :).
>
> Chris
>
> On Wed, Mar 02, 2016 at 11:21:49PM -0800, Christopher Collins wrote:
> > Nice!  That seems to work.  I guess I completely glossed over those
> > vanity URL emails.  I will make the necessary changes to the develop
> > branch.  Unfortunately, I'm afraid it is too late to fix 0.8.0-b1.
> >
> > Chris
> >
> > On Wed, Mar 02, 2016 at 10:40:53PM -0800, Sterling Hughes wrote:
> > >
> > > >
> > > > When pointed at the apache server, on the other hand, "go get" seems
> to
> > > > require the ".git" suffix.  An I mentioned earlier, this results in
> the
> > > > creation of a directory that also has the ".git" suffix.
> > > >
> > > > The problem is: the behavior of "git clone" is in conflict with the
> > > > behavior of "go get", at least with regards to the apache git server.
> > > > At one point the installation documentation was accurate, but it
> seems
> > > > we have since opted for git-friendliness rather than
> > > > go-get-friendliness.
> > > >
> > > > We will need to find a simpler workaround.  In the meantime, we
> should
> > > > at least update the documentation.  Also, soon newt binaries will be
> > > > available for download which help to alleviate problems with go.
> > > >
> > >
> > > Weren't Todd & Aditi making "mynewt.apache.org" a valid import path,
> > > that would point to the proper Apache git repository?   I thought this
> > > would solve that problem?
> > >
> > > Sterling
>

Re: installing the Newt

[Christopher Collins]

I have committed the changes to the develop branch.  Now all go imports
use the vanity domain.

Unfortunately, this is going cause a bit of pain for the current users
because the newt sources are now in the wrong directory.  To correct
this problem, you will need to move the old newt path to the new one:

$ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
  mv $GOPATH/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt 
"$GOPATH"/src/mynewt.apache.org/newt

If you plan on building older versions of newt, you should link the path
rather than move it:

$ mkdir -p "$GOPATH"/src/mynewt.apache.org &&
  ln -s $GOPATH/src/git-wip-us.apache.org/repos/asf/incubator-mynewt-newt 
"$GOPATH"/src/mynewt.apache.org/newt

Sorry for the hassle.  Yes, we definitely need to include convenience
binaries in the next release :).

Chris

On Wed, Mar 02, 2016 at 11:21:49PM -0800, Christopher Collins wrote:
> Nice!  That seems to work.  I guess I completely glossed over those
> vanity URL emails.  I will make the necessary changes to the develop
> branch.  Unfortunately, I'm afraid it is too late to fix 0.8.0-b1.
> 
> Chris
> 
> On Wed, Mar 02, 2016 at 10:40:53PM -0800, Sterling Hughes wrote:
> > 
> > >
> > > When pointed at the apache server, on the other hand, "go get" seems to
> > > require the ".git" suffix.  An I mentioned earlier, this results in the
> > > creation of a directory that also has the ".git" suffix.
> > >
> > > The problem is: the behavior of "git clone" is in conflict with the
> > > behavior of "go get", at least with regards to the apache git server.
> > > At one point the installation documentation was accurate, but it seems
> > > we have since opted for git-friendliness rather than
> > > go-get-friendliness.
> > >
> > > We will need to find a simpler workaround.  In the meantime, we should
> > > at least update the documentation.  Also, soon newt binaries will be
> > > available for download which help to alleviate problems with go.
> > >
> > 
> > Weren't Todd & Aditi making "mynewt.apache.org" a valid import path, 
> > that would point to the proper Apache git repository?   I thought this 
> > would solve that problem?
> > 
> > Sterling

Re: installing the Newt

[Justin Mclean]

Hi,

> Nice!  That seems to work.  I guess I completely glossed over those
> vanity URL emails.  I will make the necessary changes to the develop
> branch.  Unfortunately, I'm afraid it is too late to fix 0.8.0-b1.

Would be easy enough to release a 0.8.1 if people think the fix is important 
enough to be released. I know there are planned releases coming up, but that 
doesn’t mean you can have unplanned ones. In theory anyone can make a release 
and put it up for a PPMC vote.

Thanks,
Justin

Re: installing the Newt

[Sterling Hughes]

When pointed at the apache server, on the other hand, "go get" seems to
require the ".git" suffix.  An I mentioned earlier, this results in the
creation of a directory that also has the ".git" suffix.

The problem is: the behavior of "git clone" is in conflict with the
behavior of "go get", at least with regards to the apache git server.
At one point the installation documentation was accurate, but it seems
we have since opted for git-friendliness rather than
go-get-friendliness.

We will need to find a simpler workaround.  In the meantime, we should
at least update the documentation.  Also, soon newt binaries will be
available for download which help to alleviate problems with go.



Weren't Todd & Aditi making "mynewt.apache.org" a valid import path, 
that would point to the proper Apache git repository?   I thought this 
would solve that problem?


Sterling