You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Christopher Collins (JIRA)" <ji...@apache.org> on 2017/02/25 18:28:44 UTC
[jira] [Commented] (MYNEWT-293) Newt should make it easier to make
custom packages
[ https://issues.apache.org/jira/browse/MYNEWT-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884331#comment-15884331 ]
Christopher Collins commented on MYNEWT-293:
--------------------------------------------
Should `pkg clone` be renamed to `pkg copy`? This would be consistent with the `target copy` command.
> Newt should make it easier to make custom packages
> --------------------------------------------------
>
> Key: MYNEWT-293
> URL: https://issues.apache.org/jira/browse/MYNEWT-293
> Project: Mynewt
> Issue Type: Improvement
> Components: Newt
> Affects Versions: v1_0_0_beta1
> Reporter: Sterling Hughes
> Assignee: Fabio Utzig
> Fix For: v1_0_0_rel
>
>
> There are a few issues with current newt package creation:
> - It's opaque as to how to create a local package in a project.
> - Need to add two options:
> - newt pkg new <pkgname>: create a new package in the current directory, with a basic template
> - newt pkg clone <pkg-location> <pkg-dest>: Clone an existing package into the currnet directory.
> - Currently, there must be an exact match on repository descriptor, or the newt tool will barf. This should be smarter --
> - If it can't resolve a dependency in the local project, it should look at the current project/workspace, and try to resolve the package
> - It should issue a warning if it can't find the package.
> - Currently pkg.name and the name of the package directory can not match, and the pkg.name will be taken over the pkg directory. There should be a warning issued if the package directory does not match the package name.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
Re: [jira] [Commented] (MYNEWT-293) Newt should make it easier to
make custom packages
Posted by Sterling Hughes <st...@gmail.com>.
Yes!
On 25 Feb 2017, at 10:28, Christopher Collins (JIRA) wrote:
> [
> https://issues.apache.org/jira/browse/MYNEWT-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884331#comment-15884331
> ]
>
> Christopher Collins commented on MYNEWT-293:
> --------------------------------------------
>
> Should `pkg clone` be renamed to `pkg copy`? This would be consistent
> with the `target copy` command.
>
>> Newt should make it easier to make custom packages
>> --------------------------------------------------
>>
>> Key: MYNEWT-293
>> URL: https://issues.apache.org/jira/browse/MYNEWT-293
>> Project: Mynewt
>> Issue Type: Improvement
>> Components: Newt
>> Affects Versions: v1_0_0_beta1
>> Reporter: Sterling Hughes
>> Assignee: Fabio Utzig
>> Fix For: v1_0_0_rel
>>
>>
>> There are a few issues with current newt package creation:
>> - It's opaque as to how to create a local package in a project.
>> - Need to add two options:
>> - newt pkg new <pkgname>: create a new package in the current
>> directory, with a basic template
>> - newt pkg clone <pkg-location> <pkg-dest>: Clone an existing
>> package into the currnet directory.
>> - Currently, there must be an exact match on repository descriptor,
>> or the newt tool will barf. This should be smarter --
>> - If it can't resolve a dependency in the local project, it should
>> look at the current project/workspace, and try to resolve the package
>> - It should issue a warning if it can't find the package.
>> - Currently pkg.name and the name of the package directory can not
>> match, and the pkg.name will be taken over the pkg directory. There
>> should be a warning issued if the package directory does not match
>> the package name.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.15#6346)
Re: [jira] [Commented] (MYNEWT-293) Newt should make it easier to
make custom packages
Posted by Sterling Hughes <st...@gmail.com>.
Yes!
On 25 Feb 2017, at 10:28, Christopher Collins (JIRA) wrote:
> [
> https://issues.apache.org/jira/browse/MYNEWT-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884331#comment-15884331
> ]
>
> Christopher Collins commented on MYNEWT-293:
> --------------------------------------------
>
> Should `pkg clone` be renamed to `pkg copy`? This would be consistent
> with the `target copy` command.
>
>> Newt should make it easier to make custom packages
>> --------------------------------------------------
>>
>> Key: MYNEWT-293
>> URL: https://issues.apache.org/jira/browse/MYNEWT-293
>> Project: Mynewt
>> Issue Type: Improvement
>> Components: Newt
>> Affects Versions: v1_0_0_beta1
>> Reporter: Sterling Hughes
>> Assignee: Fabio Utzig
>> Fix For: v1_0_0_rel
>>
>>
>> There are a few issues with current newt package creation:
>> - It's opaque as to how to create a local package in a project.
>> - Need to add two options:
>> - newt pkg new <pkgname>: create a new package in the current
>> directory, with a basic template
>> - newt pkg clone <pkg-location> <pkg-dest>: Clone an existing
>> package into the currnet directory.
>> - Currently, there must be an exact match on repository descriptor,
>> or the newt tool will barf. This should be smarter --
>> - If it can't resolve a dependency in the local project, it should
>> look at the current project/workspace, and try to resolve the package
>> - It should issue a warning if it can't find the package.
>> - Currently pkg.name and the name of the package directory can not
>> match, and the pkg.name will be taken over the pkg directory. There
>> should be a warning issued if the package directory does not match
>> the package name.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.15#6346)