{"id":34522245,"url":"https://github.com/secondlife/3p-nghttp2","last_synced_at":"2026-05-29T17:31:05.849Z","repository":{"id":138610026,"uuid":"539703677","full_name":"secondlife/3p-nghttp2","owner":"secondlife","description":null,"archived":false,"fork":false,"pushed_at":"2024-11-22T02:33:22.000Z","size":3193,"stargazers_count":0,"open_issues_count":0,"forks_count":1,"subscribers_count":3,"default_branch":"main","last_synced_at":"2024-11-22T03:25:28.909Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Shell","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/secondlife.png","metadata":{"files":{"readme":"README.Linden","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2022-09-21T22:15:38.000Z","updated_at":"2024-11-22T02:32:36.000Z","dependencies_parsed_at":null,"dependency_job_id":"4083795f-63cc-41a6-9590-84c2678d49ca","html_url":"https://github.com/secondlife/3p-nghttp2","commit_stats":null,"previous_names":[],"tags_count":9,"template":false,"template_full_name":null,"purl":"pkg:github/secondlife/3p-nghttp2","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/secondlife%2F3p-nghttp2","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/secondlife%2F3p-nghttp2/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/secondlife%2F3p-nghttp2/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/secondlife%2F3p-nghttp2/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/secondlife","download_url":"https://codeload.github.com/secondlife/3p-nghttp2/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/secondlife%2F3p-nghttp2/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":33664259,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-05-29T02:00:06.066Z","response_time":107,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-12-24T04:59:29.202Z","updated_at":"2026-05-29T17:31:05.843Z","avatar_url":"https://github.com/secondlife.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"\n0.  Pre-Checkin Checklist\n\n    Performed from top of repo, master branch, head:\n\n    [ ]  Is tag 'current' at the head of 'vendor'?\n\n         git tag --points-at vendor\n\n    [ ]  Expected differences between vendor and master?  Very\n         little of the original source should be modified.\n\n         git diff master..vendor --compact-summary\n\n    [ ]  Are the 'vendor' and 'default' branch source directories\n         'nghttp2' and not 'nghttp2-\u003cversion\u003e'?\n\n    [ ]  Is Makefile identical to distribution?  Not strictly\n         required but a good idea.\n\n         git diff master..vendor curl/Makefile\n\n    [ ]  Examine the build logs to make certain that the data type\n         primitives and their formats are in agreement.  Good \n         example from a 32-bit Linux build:\n\n         checking size of long... 4\n         checking size of void*... 4\n         checking for 64-bit curl_off_t data type... int64_t\n         checking size of curl_off_t... 8\n         checking formatting string directive for curl_off_t... \"lld\"\n         checking formatting string directive for unsigned curl_off_t... \"llu\"\n         checking constant suffix string for curl_off_t... LL\n         checking constant suffix string for unsigned curl_off_t... ULL\n\n\n\n1.  Introduction\n\n    Build of nghttp2 library used by Curl for HTTP/2\n\n\n2.  Modifications\n\n        \n3.  Source Origin\n\n4.  Package Contents\n\n    Common:\n    * include/nghttp2/ngttp2.h\n    * include/nghttp2/ngttp2ver.h\n\n    Windows:\n    * lib/release/nghttp2.dll\n    * lib/release/nghttp2.exp\n    * lib/release/nghttp2.lib\n\n    Mac OS X (debug and release):\n\n    Linux:\n\n\n5.  Known Dependencies\n\n    This is not authoritative, it's just a reminder to followup\n    with dependent packages.\n\n    * curl\n    * viewer\n\n===================================================================\n\n               Third-Party Library Repo Structure\n\n\nIntroduction\n\nWe want to have a way to capture local modifications to a third-party\nopen-source project, such as libcurl, without needing write access to\ntheir public repository.  We want to be able to carry forward such\nmodifications to newer versions of the public project.  All this\nshould be independent of the organizational decision as to whether\nit's even desirable to try to submit our local modifications upstream.\n\nFortunately, the Subversion folks articulated a process years ago that\naddresses this very requirement.  They call it \"Vendor Branches.\"  The\nsame tactic, suitably adapted, works with Mercurial too.\n\nThe essence of the idea is that we capture and tag a particular\nsnapshot of the open-source project.  We develop our local\nmodifications to that, and the repository tip incorporates them.  But\nwhen we want to update to a newer version of the public project, we\nbring it into the repository in such a way that we can discover the\nchanges from the original snapshot and the new one -- and then have\nMercurial apply those deltas to the ''combined'' source.\n\nThe following material is adapted from\nhttp://svnbook.red-bean.com/en/1.1/ch07s05.html, the Red Bean\nSubversion book, but recast for Mercurial.  The Linden source for this\nmaterial is an internal wiki.  There may be superceding documentation\non the public wiki when you read this.  We recommend searching there\nfor updates to conventions below.  And note that each particular\nlibrary may implement variations of this scheme.\n\n\nGeneral Vendor Branch Management Procedure\n\nManaging vendor branches generally works like this.  You create a\nnamed branch (\"vendor\") to store the vendor source snapshots.  Then\nyou import the third party code into that branch.  Your modified\nbranch (named \"default\") is based on \"vendor\".  You always make your\nlocal changes to the default branch.  With each new release of the\ncode you are tracking you bring it into the \"vendor\" branch and merge\nthe changes into \"default\", resolving whatever conflicts occur between\nyour local changes and the upstream changes.\n\nPerhaps an example will help to clarify this algorithm.  We'll use a\nscenario where your development team is creating a calculator program\nthat links against a third-party complex number arithmetic library,\nlibcomplex.  We'll construct a repository specifically for our\nlocally-modified version of that library.  To begin, we must\ninitialize our repository and create at least one file in our\n\"default\" branch.\n\n $ git init ourcomplex\n $ cd ourcomplex\n $ touch README.txt\n $ git add README.txt\n $ git commit -m \"Initial\"\n\nNow we can create the vendor branch and do the import of the first\nvendor drop.  We'll call our vendor branch \"vendor\", and each\nsuccessive code drop will be tagged \"current\".\n\n $ git branch vendor\n $ git checkout vendor\n $ tar -xjf ../libcomplex-1.0.tar.bz2\n $ mv libcomplex-1.0 libcomplex\n $ git add --all\n $ git commit -m \"1.0 source drop\"\n $ git tag current\n $ git tag 1.0\n\nWe now have the current version of the libcomplex source code in\nbranch \"vendor\", tagged \"current\" and in a non-version-specific source\ncode subdirectory (\"libcomplex\").  Next, we merge it into the default\nbranch.  It is in the default branch that we will make our\ncustomizations.\n\n $ git checkout master\n $ git merge vendor\n $ git commit -m \"initial: 1.0\"\n\nWe get to work customizing the libcomplex code.  Before we know it,\nour modified version of libcomplex is now completely integrated into\nour calculator program.\n\nA few weeks later, the developers of libcomplex release a new version\nof their library, version 1.1, which contains some features and\nfunctionality that we really want.  We'd like to upgrade to this new\nversion, but without losing the customizations we made to the existing\nversion.  What we essentially would like to do is to replace our\ncurrent baseline version of libcomplex 1.0 with a copy of libcomplex\n1.1, and then have Mercurial re-apply the custom modifications we\npreviously made to that library to the new version.  But we actually\napproach the problem from the other direction, applying the changes\nmade to libcomplex between versions 1.0 and 1.1 to our modified copy\nof it.\n\nTo perform this upgrade, we update our repository to our vendor\nbranch, and update the \"current\" tag with the new libcomplex 1.1\nsource code.  We quite literally replace the existing files with the\nnew files, clearing out the whole tree and exploding the libcomplex\n1.1 release tarball in its place.  The goal here is to make the tip of\nour vendor branch contain only the libcomplex 1.1 code, and to ensure\nthat all that code is under version control.  Oh, and we want to do\nthis with as little version control history disturbance as possible.\n\n $ git checkout vendor\n $ rm -rf libcomplex\n $ tar -xjf ../libcomplex-1.1.tar.bz2\n $ mv libcomplex-1.1 libcomplex\n $ git add --all \n $ # Additional 'git add' commands if needed\n $ git commit -m \"1.1 source drop\"\n\nAfter unpacking the 1.1 tarball, hg status will show files with local\nmodifications as well as, perhaps, some unversioned or missing files.\nIf we did what we were supposed to do, the unversioned files are only\nthose new files introduced in the 1.1 release of libcomplex.  The\nmissing files are files that were in 1.0 but not in 1.1.  The 'git add\n--all' command deals with both.\n\nFor simple or stable libraries, the 'git add --all' command should be\nreliable.  For more complicated libraries subject to refactoring or\nlarge gaps of time between updates (e.g. libcurl), it can get a little\nlost trying to match files in the old release with files in the new\nrelease.  Pay attention to the output of the command or better still,\ndo dry runs.  Files erroneously moved can be excluded with the '-X'\noption and then dealt with individually with 'git add' and 'git rm' or 'gim mv'\ncommands after the initial 'git add --all'.  \n\nThe 'add --all' process doesn't have to be perfect.  Recreating the\nevolution of the upstream source tree isn't universally practical.\nBut we'd like to capture movement of files in the vendor branch that\nare modified in the default branch.  If achieving that becomes too\ntedious, then re-implementation of the default branch edit in a new\nfile is fine.  Just note it here for the next developer.\n\nFinally, once our current working copy contains only the libcomplex\n1.1 code, we commit the changes we made to get it looking that way.\n\nOur current vendor branch now contains the new vendor drop.  We move\nthe 'current' tag to the new version (in the same way we previously\ntagged the version 1.0 vendor drop), and then merge the differences\nbetween the version 1.0 and version 1.1 into our default branch.\n\n $ git tag --force current\n $ git tag 1.1\n $ git checkout master\n $ git merge vendor\n # resolve all the conflicts between their changes and our changes\n # if you will have conflicts in .hgtags, simply take *all* lines\n ...\n $ git commit -m \"update with 1.1\"\n\nAny additional work needed to get the merged library working can\nnow be done on the default branch.\n\n\nRevision Tags\n\nWe don't currently make use of Mercurial tags in the build and release\nprocess for 3rd-party libraries.  But we would like to establish a\nconvention to document update and release points.  The tags we would\nlike to establish are:\n\n * 'current' Points to a succession of vendor releases checked into\n   the 'vendor' branch.  Will almost always be at or close to branch\n   head.\n\n * '\u003cversion\u003e' Tag on the 'vendor' branch pointing to a verbatim\n   checkin of a 3rd-party's \u003cversion\u003e release.  Example:  '7.21.1' for\n   a particular version of libcurl we have used.\n\n * Release-type tags on the default branch aren't as useful given how\n   Mercurial handles tags and how autobuild works.\n\n\nSchematic of a Third-Party Repository\n\nBelow is the output of the 'hg glog' command showing a library project\ngoing through an initial 1.0 release and an update from the vendor to\n1.1.  Significant revisions in the repository lifecycle are as\nfollows:\n\n 0  Creation of the repo with an initial file.\n 1  1.0 code drop on branch 'vendor'\n 4  Merge of 1.0 code onto branch 'default'\n 5  Modifications to library we wish to keep over time.  Released.\n 6  1.1 code drop on branch 'vendor'\n 9  Merge of 1.1 code onto branch 'default'\n10  Fixes to merge yielding production 1.1 library.  Released.\n \n\n@  changeset:   10:888229641f6e\n|  tag:         tip\n|  user:        Monty Brandenberg \u003cmonty@lindenlab.com\u003e\n|  date:        Wed Oct 30 13:35:51 2013 -0400\n|  summary:     Work to get 1.1 merge working.  Release.\n|\no    changeset:   9:925ccdf09f50\n|\\   parent:      5:83c5775c23dc\n| |  parent:      8:977001a08e48\n| |  user:        Monty Brandenberg \u003cmonty@lindenlab.com\u003e\n| |  date:        Wed Oct 30 13:35:20 2013 -0400\n| |  summary:     update with 1.1\n| |\n| o  changeset:   8:977001a08e48\n| |  branch:      vendor\n| |  user:        Monty Brandenberg \u003cmonty@lindenlab.com\u003e\n| |  date:        Wed Oct 30 13:33:49 2013 -0400\n| |  summary:     Added tag 1.1 for changeset 5f6cb89add91\n| |\n| o  changeset:   7:59bce0f6d12f\n| |  branch:      vendor\n| |  user:        Monty Brandenberg \u003cmonty@lindenlab.com\u003e\n| |  date:        Wed Oct 30 13:33:41 2013 -0400\n| |  summary:     Added tag current for changeset 5f6cb89add91\n| |\n| o  changeset:   6:5f6cb89add91\n| |  branch:      vendor\n| |  tag:         current\n| |  tag:         1.1\n| |  parent:      3:8525ad934ecd\n| |  user:        Monty Brandenberg \u003cmonty@lindenlab.com\u003e\n| |  date:        Wed Oct 30 13:33:29 2013 -0400\n| |  summary:     1.1 source drop\n| |\no |  changeset:   5:83c5775c23dc\n| |  tag:         1.0\n| |  user:        Monty Brandenberg \u003cmonty@lindenlab.com\u003e\n| |  date:        Wed Oct 30 13:32:31 2013 -0400\n| |  summary:     Linden-specific changes to the library.  Release\n| |\no |  changeset:   4:bccb736585f4\n|\\|  parent:      0:400e4516c406\n| |  parent:      3:8525ad934ecd\n| |  user:        Monty Brandenberg \u003cmonty@lindenlab.com\u003e\n| |  date:        Wed Oct 30 13:31:40 2013 -0400\n| |  summary:     initial:  1.0\n| |\n| o  changeset:   3:8525ad934ecd\n| |  branch:      vendor\n| |  user:        Monty Brandenberg \u003cmonty@lindenlab.com\u003e\n| |  date:        Wed Oct 30 13:30:21 2013 -0400\n| |  summary:     Added tag 1.0 for changeset 8ac3828d03bb\n| |\n| o  changeset:   2:7aa1a1cb62d9\n| |  branch:      vendor\n| |  user:        Monty Brandenberg \u003cmonty@lindenlab.com\u003e\n| |  date:        Wed Oct 30 13:30:14 2013 -0400\n| |  summary:     Added tag current for changeset 8ac3828d03bb\n| |\n| o  changeset:   1:8ac3828d03bb\n|/   branch:      vendor\n|    tag:         1.0\n|    user:        Monty Brandenberg \u003cmonty@lindenlab.com\u003e\n|    date:        Wed Oct 30 13:30:09 2013 -0400\n|    summary:     1.0 source drop\n|\no  changeset:   0:400e4516c406\n   user:        Monty Brandenberg \u003cmonty@lindenlab.com\u003e\n   date:        Wed Oct 30 13:29:16 2013 -0400\n   summary:     Created repo with initial readme file\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsecondlife%2F3p-nghttp2","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsecondlife%2F3p-nghttp2","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsecondlife%2F3p-nghttp2/lists"}