[jira] [Updated] (MYNEWT-310) newt should globally namespace remote repositories
[ https://issues.apache.org/jira/browse/MYNEWT-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins updated MYNEWT-310: --- Fix Version/s: (was: v1_1_0_rel) > newt should globally namespace remote repositories > -- > > Key: MYNEWT-310 > URL: https://issues.apache.org/jira/browse/MYNEWT-310 > Project: Mynewt > Issue Type: New Feature > Security Level: Public(Viewable by anyone) >Reporter: Sterling Hughes >Assignee: Christopher Collins > > Right now remote repositories can have conflicting names (e.g. somebody else > could reserve apache-mynewt-core, and newt wouldn't have a way of resolving > the conflict.) > Need some form of global namespacing on repository descriptors, whether using > the DNS name (ala go), or some other sort of registry. > This will become important once inter-repository dependencies and mirroring > come into play. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-310) newt should globally namespace remote repositories
[ https://issues.apache.org/jira/browse/MYNEWT-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sterling Hughes updated MYNEWT-310: --- Fix Version/s: (was: v1_0_0_beta1) v1_1_beta1 > newt should globally namespace remote repositories > -- > > Key: MYNEWT-310 > URL: https://issues.apache.org/jira/browse/MYNEWT-310 > Project: Mynewt > Issue Type: New Feature >Reporter: Sterling Hughes >Assignee: Christopher Collins > Fix For: v1_1_beta1 > > > Right now remote repositories can have conflicting names (e.g. somebody else > could reserve apache-mynewt-core, and newt wouldn't have a way of resolving > the conflict.) > Need some form of global namespacing on repository descriptors, whether using > the DNS name (ala go), or some other sort of registry. > This will become important once inter-repository dependencies and mirroring > come into play. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MYNEWT-310) newt should globally namespace remote repositories
[ https://issues.apache.org/jira/browse/MYNEWT-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sterling Hughes updated MYNEWT-310: --- Assignee: Christopher Collins > newt should globally namespace remote repositories > -- > > Key: MYNEWT-310 > URL: https://issues.apache.org/jira/browse/MYNEWT-310 > Project: Mynewt > Issue Type: New Feature >Reporter: Sterling Hughes >Assignee: Christopher Collins > Fix For: v1_0_0_beta1 > > > Right now remote repositories can have conflicting names (e.g. somebody else > could reserve apache-mynewt-core, and newt wouldn't have a way of resolving > the conflict.) > Need some form of global namespacing on repository descriptors, whether using > the DNS name (ala go), or some other sort of registry. > This will become important once inter-repository dependencies and mirroring > come into play. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MYNEWT-310) newt should globally namespace remote repositories
[ https://issues.apache.org/jira/browse/MYNEWT-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sterling Hughes updated MYNEWT-310: --- Fix Version/s: (was: v0_10_0) v1_0_0_beta1 > newt should globally namespace remote repositories > -- > > Key: MYNEWT-310 > URL: https://issues.apache.org/jira/browse/MYNEWT-310 > Project: Mynewt > Issue Type: New Feature >Reporter: Sterling Hughes >Assignee: Christopher Collins > Fix For: v1_0_0_beta1 > > > Right now remote repositories can have conflicting names (e.g. somebody else > could reserve apache-mynewt-core, and newt wouldn't have a way of resolving > the conflict.) > Need some form of global namespacing on repository descriptors, whether using > the DNS name (ala go), or some other sort of registry. > This will become important once inter-repository dependencies and mirroring > come into play. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
