changes are ready for commit now, i just want to make sure to give folks
to voice an opinion.
but: we can always revert this too -- i'd prefer not to have to merge w
mainline for too long/would like folks to pick these changes up quickly
given impending b1.
sterling
On 2/9/16 4:57 PM, marko kiiskila wrote:
+1.
This will have effect on pending work. When do you think you’ll do this?
IMHO sooner is better.
On Feb 9, 2016, at 3:56 PM, Sterling Hughes <[email protected]> wrote:
Hey,
I have implemented the bug report here:
https://issues.apache.org/jira/browse/MYNEWT-71
I think everyone has noticed that on-boarding new users becomes difficult
because we use custom terms for packages, package lists and repositories.
While I personally like these terms (I named them that way), I think we wan the
package and build system to be as easy to use as possible, and keeping track of
these seems to be creating too much of a hurdle.
So, I have a bunch of mondo commits to rename these. They are low risk, and
I've tested them.
When I commit, in order to maintain your existing targets, you will need to do
the following:
- rename .nest in larva to .repo (this is custom per install, so I can't move
this for you)
- rename nest.db to repo.db in .repo
- rename clutches/ directory pkg-lists/ in .repo
Everything else should operate well, unless you have changes to egg.yml files
that are uncommitted. You will need to manually port those over.
Also, as a part of this commit, I've removed .git from the newt import path.
It seems like the majority of people are able to go get this without the .git,
and it was causing conflicts with newtmgr. (*)
I'll push these to origin master this evening if nobody has objections.
Sterling
(*) These will eventually be moved, again, when Todd adds mynewt.apache.org
support.
