On 7 December 2010 11:01, Steven Shiau <[email protected]> wrote: > > > On 2010/12/5 上午 07:09, Michal Suchanek wrote: >> >> On 4 December 2010 16:08, Steven Shiau<[email protected]> wrote: >>> >>> Thanks for all the discussions here. Clonezilla is _NOT_ perfect, that's >>> why we keep improving that. >>> If you think it sucks, yet it's still worthy to you, and you are capable >>> of coding, please create patch files and we will be very happy to take >>> that. >> >> I am capable of coding but one of the reason why clonezilla sucks is >> that the "source" comes with no documentation whatsoever. > > Or could you please give us a good example how to have a good doc about the > source? We will do our best to fill this.
Good source does not need much in the way of docs because it uses well established build process. Eg. C sources can use autotools which provide their own generic document for building an autotools managed project. Since Clonezilla is debian-live based it could provide a debian-live configuration auto/ and config/ directories which then can be built by simply unpacking the source and typing "lb build". This however requires that all software which is not part of debian be either distributed in the source tarball or put on a publicly accessible properly signed apt repository. If you need help with setting up an apt repository I can send you the script which I use to create mine. It is a one use script and is far from perfect but should be easily adapted for other repositories. I can understand that software is in development and is not always in state to be built this easily. Still you can provide a README file which details - what tools are used to build the source Eg. we build on distribution X version Y.Z using T version A.B.C and U version D.E.F - what steps are required to build - this should record all the commands you type into the terminal after you unpack the source to obtain the built program - what you get - name the built files and their purpose (this is typically only required when complex makefiles or build scripts with multiple build results are used) Thanks Michal ------------------------------------------------------------------------------ What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d _______________________________________________ Clonezilla-live mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clonezilla-live
