Geoffroy Vallée wrote: > Hi Andrea, > > I agree with what you say but because of a lack of free time, if you do not > mind, i prefer to focus on the current systemimager-debian code in order to > create a new set of packages for debian unstable. I will be happy to work > with you on the "integration" in the main repo later on. I just do not want > to work on too many points and at the end do not progress on any of these > points.
Totally agree. > > To summarize, i think we can organize the Debian into two phases: > - create of new packages for Debian unstable, > - based on your effort, see if you integrate the "official trunk". I also > think that for this phase we will have first to figure out few points before > to do the actual integration, Debian imposes few constraints. > OK. I would reformulate your proposal in the following plan: - first step is to include systemimager 3.8.x in Debian unstable, and I'm considering this task totally based on the work you've done in systemimager-debian code - in parallel I'll continue the work to have a very simple and basic integration of the official trunk in Debian (I mean: automatically create debs from trunk with a single command and those debs respect a big part of all the required Debian constraints) - when both activities are considered *stable* (= first derivative of the needed development activity very close to 0) we'll try merge our works into the official trunk Thanks, -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
