Skip to content

RFC Patch and dependency management #1384

Closed

Description

@OwenBrotherwood

The original comment is removed as it was rather long and focused on a risk suppliment for patch and dependancy management which is now in AAA

The original comment went from Patch/Dependancy thru to Github in general regard to issue 1380


current focus is npm and issue management

Activity

  1. ritch commented on May 13, 2015

    @ritch
    Member

    I don't think this is the right place for this. I don't see anything really actionable and thats what we like to keep the issue list populated with.

  2. changed the title [-]RFC Patch and dependancy management[/-] [+]RFC Patch and dependency management[/+] on May 18, 2015
  3. OwenBrotherwood commented on May 20, 2015

    @OwenBrotherwood
    ContributorAuthor

    NPM Notes Whys and Whats

    nodejs/node-v0.x-archive#5132 (comment)
    CPAN and why npm (at least a bit of the why)

    https://www.youtube.com/watch?v=ShRDgdvlZQ8 issacs 2011 npm

    http://howtonode.org/introduction-to-npm

    Dependency Hell Isn't Fun
    Most systems have a single root namespace. That kind of sucks. 
    If two different things depend on different versions of the same dependency, then you've got two options:
    
    Statically compile the dependency into the program.
    Hate life.
    Option #2 is Not Fun. So eff that noise. That sucks, and is dumb.
    
    Option #1 is less than ideal if you want to be able to abstract out 
    parts of your program and benefit from updates to the dependencies.
    
    Thankfully, unlike most programming environments, the CommonJS Securable Module 
    system lets you avoid dependency hell by modifying the require.paths at runtime, so that each package sees the version that it depends on.
    
    I think that's pretty cool.
    

    1380#issuecomment-103976583

    node is an exception:: why?
    or rather node_modules (patch and dependancy)?

    Find out more of sam's stuff
    https://strongloop.com/strongblog/update-to-installer/ *** gotta read as gives profile of sams work and his view's background
    https://vimeo.com/77870958


    http://semver.org/

    Given a version number MAJOR.MINOR.PATCH, increment the:
    
    MAJOR version when you make incompatible API changes,
    MINOR version when you add functionality in a backwards-compatible manner, and
    PATCH version when you make backwards-compatible bug fixes.
    Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
    

    Find out where this is a problem

    • branches
    • tags
    • repos don't seem to give a problem : google more

    Tie in to npm https://docs.npmjs.com/getting-started/semantic-versioning
    https://docs.npmjs.com/misc/semver

    Also, going back to LoopBack. Using seperate modules for distinct components allows them to be
     independently semvered, and to have their majors get bumped so then can be iterated on quickly
     without effecting the stable major release.
    

    hmmm, that could be a problem.
    Anything reusable has to have its own life (semver) as it gets hit by different dependants/dependancies.
    but again, the package.json refers to semver and placement to get the code, and the placement can contain tag or branch (but there is something nagging me, there is a problem here:that my little knowledge of npm may be hiding ((back to doc and packaging)) )


    npm as a tool contra github/git as a tool : if there is a conflict, where does one gain most in using the one or the other even when it decreases the value of the other. gain contra pain


    npm strength/weekness
    npm uses package.json
    package.json

    • describes where to get the code plus "other stuff"
    • describes versions (version hell in node_modules: double check if true)

    Understand the tooling /snowflake etc in rmg's comment

    • developers make magic
    • the support / tool /test get the problems latter: make sure one has a balanced distribution of problems that due to a wrong turning, cause huge problems down the road: been there, done that

    npmjs.org + semver
    npmjs,org is a place to find package.json via a npm, a (the) package for node.
    https://docs.npmjs.com/
    https://docs.npmjs.com/misc/config
    https://docs.npmjs.com/enterprise/github
    https://docs.npmjs.com/misc/developers

    What is a package
    
    A package is:
    
    a) a folder containing a program described by a package.json file
    b) a gzipped tarball containing (a)
    c) a url that resolves to (b)
    d) a <name>@<version> that is published on the registry with (c)
    e) a <name>@<tag> that points to (d)
    f) a <name> that has a "latest" tag satisfying (e)
    g) a git url that, when cloned, results in (a).
    Even if you never publish your package, you can still get a lot of benefits of using npm if you just want to write a node program (a), and perhaps if you also want to be able to easily install it elsewhere after packing it up into a tarball (b).
    
    Git urls can be of the form:
    
    git://github.com/user/project.git#commit-ish
    git+ssh://user@hostname:project.git#commit-ish
    git+http://user@hostname/project/blah.git#commit-ish
    git+https://user@hostname/project/blah.git#commit-ish
    The commit-ish can be any tag, sha, or branch which can be supplied as an argument to git checkout. The default is master.
    

    https://github.com/strongloop/loopback/blob/master/package.json

    Still no problem with a mega-repo that uses branches and tags ...?


    global contra non-global packages


    find more multi-repro hell examples when using github as a tool to leverage goals of a project


    https://youtu.be/tgTniHwGPuM?t=5m33s Bert Belder in dependancy hell
    side video
    https://www.youtube.com/watch?v=1C5-A-BgPM8 Belder War: apparently it was Belder that got node to windows AND they mentioned CPAN and Perl (at last)
    Latter research showed that isaacs/npm was looking at CPAN a lot but Belder War named it first in my research


    No real reference to JSAN as yet (Javascript CPAN that never took off) and no reasons given for why reinvent the wheel by creating npm

  4. OwenBrotherwood commented on May 21, 2015

    @OwenBrotherwood
    ContributorAuthor

    Subtree

    http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/

    Conclusions
    After having used submodule for a while I appreciate git subtree much more, 
    lots of submodule problems are superseded and solved by subtree. 
    As usual, with all things git, there is a learning curve to make the most of the feature.
    

    https://lostechies.com/johnteague/2014/04/04/using-git-subtrees-to-split-a-repository/
    https://makingsoftware.wordpress.com/2013/02/16/using-git-subtrees-for-repository-separation/


    http://www.mos6581.org/git_subtree_alternative


    I had wondered if someone would come with subtree 👍
    But git is a real git: other ways ..hmm, cannot remember so more googling


    I wonder if @bnoordhuis has some basic structural ideas that I could play with based on what he has been thinking


    Issue management, enable Issues on a fork to allow issues: geeze how did I miss that :(

    https://github.com/OwenBrotherwood/loopback/issues/1
    https://github.com/coolPlask/loopback/issues/1

  5. OwenBrotherwood commented on May 26, 2015

    @OwenBrotherwood
    ContributorAuthor

    https://github.com/sloopback/sloopback-issues/wiki
    Shows the process tags I use as a community developer to aid process management

    There is a special issues repro that is the only place for issues https://github.com/sloopback/sloopback-issues
    With only ONE place for community issues, multi-repo hell for where to start an issue is avoided: where an issue is a story, the issue can be places in the correct repo for work (concept of upstream / downstream issues)


    I noted that @bajtos (@rmg) has a repo for issue summary https://github.com/strongloop/gill

    • probably to try and have some overview of issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions