Hi Per at 18.01.2012 08:32, Per Sjoholm wrote: > On 01/17/2012 05:18 PM, KP Kirchdoerfer wrote: >> Am 17.01.2012 08:40, schrieb Per Sjoholm: >>> Thanks I tried libpt.... never occurred in my mind to check for lpt... >>> Coming from leaf 2.0 I really like 4.2. >>> >>> Usually I load the package with apkg and use the text via mhttpds as a >>> guide. >>> >>> Suggestion >>> It seems that it should be possible to to have some Packages Requires >>> statements in a file. >>> that could be read by applications. >>> >>> * Build system creates Package Requirments file(PRfile) that is part of >>> package. >>> >>> * App/lrp for >>> * Lists all available lrp local and/or on net (repository) (reads >>> PRfile) >>> * Can assist with installing via ncurses and web. >>> * PXE installing would benefit from this as well as other >>> configuration/install engines >>> * signed lrp would be a requirement when loading from net. >>> >>> What fields would be good to have in a Package Requirments file and what >>> should the file >>> be called ? >>> >>> Ideas ? >>> >> Hi Per, hi to everyone; >> >> pls see: >> >> http://sourceforge.net/apps/trac/leaf/ticket/2 >> http://sourceforge.net/apps/trac/leaf/ticket/57 >> >> Any help is welcome. >> >> regards kp > A workable solution for Ticket 2 and 57 is needed and it's seems straight > forward. > I suspect that it's more to it that meets the eye hence the time. > > A first step with a simple solution that can be refined when we see the > overall consequences. > lrp format is a tar.gz and if we add a file that can be used at install time > to it. > > I would suggest a stepwise approach. > Break down into smaller parts that can be implemented stepwise. > Build the unix way ie build a program that uses existing parts like apkg. > > When the parts are working together, > then we can consolidate and also chose a different implementation if needed. > Maybe use python as a base for system mgmt tasks, it has most of what we need.
Not another piece of bloatware please. > > A file that can be handled with available shell, sed, awk, perl or just use > make. Yes, but its another big piece. I would rather suggest to add some preinstall/postinstall scripts which by themselves just call apkg with the correct parameters and can be eval(ed) keep it simple stupid > Maybe a kind of MetaData/Manifest that states what is Required and list files > with a sha256sum. > This Manifest can be signed with a Key. Which has another prerequisite, which may or may not be available at system start. cheers Erich
smime.p7s
Description: S/MIME Kryptografische Unterschrift
------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! 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-d2d
_______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
