You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Sterling Hughes (JIRA)" <ji...@apache.org> on 2016/05/11 21:57:12 UTC
[jira] [Created] (MYNEWT-293) Newt should make it easier to make
custom packages
Sterling Hughes created MYNEWT-293:
--------------------------------------
Summary: 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: v0_9_0_rel
Reporter: Sterling Hughes
Assignee: Sterling Hughes
Fix For: v0_9_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.4#6332)