From: Dennis H. <dh...@fi...> - 2003-12-29 16:43:47
|
I'm glad some progress is being made for this. I added the packaging code into Tiki in the hope that this would be helpful with this effort. As you identify groups of files that are exclusive to a feature, you can put them into a zip archive and they will then act as a package, allowing you to install and un-install them. There are also specially named SQL scripts that could be used to re-move and add the DB objects if desired. I tested this with the avatar images and it worked quite well. I have also built 2 applications that use Tiki and was thinking about uploading them into CVS. All the apps could be removed for the tiki-lite version to make the download smaller, or included in the main release to make an "all-in-one" tiki for people with no bandwidth/space concerns. I'd like more feedback from the other devs about when and how to add packages. Dennis > Well, as some of you are aware, I've been working on a script that mose > has originally started to strip away non-core items from the existing > Tiki (HEAD) installation. > > The objectives of this script (which I think may differ from the > original definition of TikiLite) are to reduce Tiki down to its bare > minimum. The installation is already 21MB from the original 44MB. > > The objectives as I see them are: > > * isolate features so that dependencies become more obvious, leading on > to creation of TikiPackager and other TikiCore work > > * create a Tiki application framework for integration and development of > new applications > > * implement changes for WYSIWYCU coding > > There are probably more, feel free to add to the list. > > Maintenance and configuration of the script is fairly easy - I've tried > to group features together, so should you require a feature, you comment > it and its dependencies out of the file, do a 'cvs up' and re-run the > script to activate changes. This is the first step to isolating features > for automated installation scripting. > > I've already made a few discoveries of dependencies - such as > commentslib.php is dependent on webmail (who would have thought :) ). > > With regard to WYSIWYCU, I've already started making changes to Tiki > HEAD code, with an introduction of $lib_libraryname variables, which > validate that a library exists and any features dependent on this > library are enabled or disabled accordingly. If the library is missing, > the checkbox is replaced with a 'Not Installed'. See $lib_spellcheck in > tiki-setup.php and tiki-admin-include-wiki.tpl. I know that > tiki-setup.php is not the correct place for library checking and will > change it later when I find where. > > The name of the script is doc/devtools/tikilite.sh. Execute it from the > top of you tiki installation. > > See http://tikiwiki.org/tiki-index.php?page=TikiLite for more info. > > -- > > Stephan Borg > LinuxSOE Pty Ltd - Linux System Integration > Phone/Fax: (02) 4754 5036 > Mobile: 0402 789 788 > Email: sb...@li... > Web: http://www.linuxsoe.com > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Tikiwiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > |