Re: A proposal for a package management system
"Gilles Espinasse" <[email protected]>
| Newsgroups | gmane.comp.security.ipcop.devel |
|---|---|
| Message-ID | <029d01ccde89$b5469790$f9b5a8c0@pii350> |
----- Original Message ----- From: "G.W. Haywood" <[email protected]> To: <[email protected]> Sent: Sunday, January 29, 2012 1:47 PM Subject: Re: [IPCop-devel] A proposal for a package management system > Hi there, > > On 24-29 Jan 2012, Gilles Espinasse and Olaf Westrik wrote: > > > > > Yes package management is for me a priority on next version... > > > > > > What for? > > > > Faster update first. > > > > We have fix for 2.0.3 that could have been delivered one month ago. > > Please can someone explain to me in simple terms exactly why the lack > of a built-in package management system is delaying the propagation of > IPCop updates by periods of the order of months? > > -- A package management allow to deliver exactly one part without touching anything else. We could mostly to the same with our update system except that there is still some manual operations needed. Release manager check : - if new files are really include using previously ./make.sh check_files (now made at each build), - probably too if old files are really suppressed as they should on installed machine. Update package signature too is manual. That would be very hard to scale to an update per day, maybe doable to an update per week. Plus when you have something not yet commited but that you build in your tree, you would not want to publish an update in those conditions. Concerning the period between updates, that's Olaf that cut the update. Gilles ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2