{"action":"opened","issue":{"url":"https://api.github.com/repos/chrsmith/windows-package-manager/issues/257","labels_url":"https://api.github.com/repos/chrsmith/windows-package-manager/issues/257/labels{/name}","comments_url":"https://api.github.com/repos/chrsmith/windows-package-manager/issues/257/comments","events_url":"https://api.github.com/repos/chrsmith/windows-package-manager/issues/257/events","html_url":"https://github.com/chrsmith/windows-package-manager/issues/257","id":59267743,"number":257,"title":"Announcing our npackd fork","user":{"login":"GoogleCodeExporter","id":9614759,"avatar_url":"https://avatars.githubusercontent.com/u/9614759?v=3","gravatar_id":"","url":"https://api.github.com/users/GoogleCodeExporter","html_url":"https://github.com/GoogleCodeExporter","followers_url":"https://api.github.com/users/GoogleCodeExporter/followers","following_url":"https://api.github.com/users/GoogleCodeExporter/following{/other_user}","gists_url":"https://api.github.com/users/GoogleCodeExporter/gists{/gist_id}","starred_url":"https://api.github.com/users/GoogleCodeExporter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GoogleCodeExporter/subscriptions","organizations_url":"https://api.github.com/users/GoogleCodeExporter/orgs","repos_url":"https://api.github.com/users/GoogleCodeExporter/repos","events_url":"https://api.github.com/users/GoogleCodeExporter/events{/privacy}","received_events_url":"https://api.github.com/users/GoogleCodeExporter/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-27T17:32:13Z","updated_at":"2015-02-27T17:32:13Z","closed_at":null,"body":"```\nHello there, \n\nFirtstly, I agree that this is not an issue at all but it seems that this is \nthe only place (other than twitter) where I can publicly post to the npackd \ncommunity.\n\nI am writing you to announce that we (at my company, HydrOcean) are currently \nworking on a customized (not a lot) version of npackd (wpmcpp). \n\nThis version aims different goals: \n\n*** Give our internal users an already configured and ready to use installation \nfor our custom repositories ***\n\nOur users no longer have to set custom repositories and directories, everything \nis embedded in our own versions of the installers. Also, we now can apply \nspecific rules like the possibility to reinstall msi packages when externally \ninstalled but detected by npackd. Allowing things like defining a same package \ninstallation directory as the one managed by npackd and reusing it in a \n<variable> dependency property. \n\n*** Improve npackd (wpmcpp) with internally developed functionalities which we \nexpected to have on the official version ***\n\nAs we cannot afford waiting for the required functionalities to be developed, \nwe have to develop it by ourselves and eventually push them to the official \nrepositories if useful for the masses. We are already proceeding this way on \n(GNU/) Linux with the NixOS distribution <http://nixos.org> and it is working \nlike a charm, close to the community. If you are interested in *nix, I \nrecommend you to look at it, the Nix package manager (on which it is based on) \naims to be the \"state of the art\" one. \n\n*** Improve our internal stability by fully manage our package management \nsystem ***\n\nThanks to this \"parallel\" version, we should be able to upgrade out entire \ncomputer base packages while being sure of the actions being applied by the \nupdate processes and eventually customizing it. \n\n*** Respect the GPL ***\n\nBecause npackd is licensed over the GPL, we must publish the source code when \nredistributed. Even if we currently do not plan to do so, we may have to \nredistribute it to our clients or partners (USB/DVD installers, development \nenvironment builders, ...) aside of our commercially developed software. \n \nBe aware that our goal is only to make our npackd custom version working \nexactly as we expect, we do not intend at all to take some leadership over the \nofficial npackd project or to affect how the software should work for the \nothers. We have totally different commercial activities and we do not intend to \ninvest on npackd more than making it work as we expect for our own \nrequirements. \n \nBecause all of our internal code is based on git and we do not have the time to \nhandle one more SCM system, we have published our fork of npackdcpp on github \nat the url <https://github.com/HydrOcean/npackdcpp>. We would enjoy some \ndiscussions about the commits and eventually merge them to the official source \ncode if you want to ;-)\n \nFinally, as we have already started to work on the source code, here are some \nof the changes already pushed on our branch that the community may appreciate \n(much more detailed descriptions are available in the commit descriptions on \n<https://github.com/HydrOcean/npackdcpp/commits/ho-master>):\n* Ask the user to create the npackd installation path if it does not exists\n* Set the default installation directory to `QDir::rootPath() + \"npackd\"\n* Support invalid certificate authorities by prompting the user\n* Support local repositories and files\n* Possibility to create directory trees for the <important-file> shortcuts\n* Source code compatible with Visual C++ 2010 (no npackcl yet; should also be \nOK for other VC++ versions compatible with Qt 4)\n* Installers for VC10 32 and 64 bit\n```\n\nOriginal issue reported on code.google.com by `bbenoist...@gmail.com` on 19 Jun 2013 at 11:09"}}