Re: [buildout] "private" releases
Adam GROSZER <[email protected]>
| Newsgroups | gmane.comp.web.zope.devel |
|---|---|
| Message-ID | <[email protected]> |
Hello, On Fri, 25 Mar 2011 19:24:05 +0000 you wrote: > > Hi Christian, > > On 25/03/2011 16:49, Christian Theune wrote: >> the German speaking Zope Users Group (DZUG e.V.) organizes a series of 4 >> sprints this year to support feature development within the proximity of >> the ZTK and solve problems encountered by Zope, Plone and Python developers. >> > <snip> >> Topics >> ====== >> >> * Discussing how to deal with "private" releases > > FWIW, I've had no problems with this, here's a sample buildout.cfg: > > [buildout] > extensions = lovely.buildouthttp > find-links = https://example.com/password/protected/folder > > ...and just dump the .tgz sdists in that folder. > > Of course, if you don't need password protection such as when you have > your "egg server" on a private network, you just need the find-links. > > I'm not really sure why people have written a complicated array of "egg > servers" and the like when a simple http or file system served folder is > just fine ;-) Well the problem is that it's not always so simple. For me a release process is preferably a single command or a single click on a button. -- Best regards, Adam GROSZER -- Quote of the day: To look up and not down, To look forward and not back, To look out and not in, and To lend a hand. - Edward Everett Hale _______________________________________________ Zope-Dev maillist - [email protected] https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )