Your use of the packages on this site means you understand they are not supported or guaranteed in any way. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.įortunately, distribution rights do not apply for internal use. If you are an organization using Chocolatey, we want your experience to be fully reliable.ĭue to the nature of this publicly offered repository, reliability cannot be guaranteed. Human moderators who give final review and sign off.Security, consistency, and quality checking.
ModerationĮvery version of each package undergoes a rigorous moderation process before it goes live that typically includes: But aside from that, if you actually follow their workaround, it should work just fine - as I understood your problem was that you didn't follow their workaround, then you blamed them for the resulting file conflicts.Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community. The only bit I'll give you is that the workaround isn't user-friendly, and that they should probably leave a note mentioning the much-more-user-friendly plugins in the Trigger Examples. > and are happy to tell people to take awful workarounds ), you need an online storage provider plugin (e.g. If one of the files to be synchronized is stored in an online storage (like e.g. > and not mention that it can be resolved with a plug-in anywhere on the main siteĪgain, you're accusing them of something that's false! They very much do see this as core functionality and explicitly tell you how to synchronize right there in the synchronization section : The fact that they don't consider syncing a core part of the password manager
0 kommentar(er)
