Skip to content
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.

Optimize output size of kpm pack #667

Merged
merged 1 commit into from
Sep 30, 2014
Merged

Conversation

ChengTian
Copy link
Contributor

parent #652

@@ -13,6 +14,7 @@ public class GlobalSettings

public IList<string> SourcePaths { get; private set; }
public string PackagesPath { get; private set; }
public IDictionary<Library, string> LibrarySHAs { get; private set; }
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PackageHashes

@ChengTian
Copy link
Contributor Author

@davidfowl , changed based on feedbacks. Also implemented the idea mentioned by you and @lodejard last Friday and successfully reduced the number of PackPackage instances.

var library = new Library()
{
Name = property.Name,
Version = SemanticVersion.Parse(dependencies[property.Name]["version"].ToString())
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to be more defensive here.

@davidfowl
Copy link
Member

:shipit:

@ChengTian ChengTian force-pushed the optimize-output-size-of-kpm-pack branch from 3355b19 to 78c8ec3 Compare September 30, 2014 05:55
- Nupkgs, nuspecs and SHA files are not copied to output packages folder
- Only copy assemblies needed by the frameworks being packed with
- Use frameworks in project.json if '--runtime' was not specified
- Use values of '--runtime' to filter frameworks in project.json
- Use SHAs from global.json when resolving KRE_PACKAGES_CACHE
- Copy tools dlls from source packages to bin folder of output
@ChengTian ChengTian force-pushed the optimize-output-size-of-kpm-pack branch from 78c8ec3 to 7119cb3 Compare September 30, 2014 06:00
@ChengTian ChengTian merged commit 7119cb3 into dev Sep 30, 2014
@ChengTian ChengTian deleted the optimize-output-size-of-kpm-pack branch September 30, 2014 06:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants