frederic rech wrote: > [snip] I'm afraid we don't talk about the same thing, may I say > "again" without being unfriendly to your eyes please ! > > Let me explain : you put on the cd only the applis to have a > functional system. About 150 Mo I think, but not sure. Anyway, let say > the stuff is small enough to be contained on a cd, ok ? > On the same cd, you create a directory, you can call it "applis" or > whatever you like. > In this dir, you create commands, the same you can make with a right > clic on the destop and choose "create a launcher". > These commands are : apt-get install appli1 appli2 appli3... let say > you can make a command for sound applis, one for graphism, one for > video, etc... > And of course you need to put a text file on the cd, to explain people > what to do ! > > Get it ? >
Hi Frederic :) I'm not really sure if I do understand it right. It's possible to write shell scripts that does 'apt-get install audio-app1 audio-app2 audio-app3' and another script that runs 'apt-get install video-app1 video-app2 video-app3'. But anyhow you need to take care about the enabled and disabled repositories before you can run such scripts. If you are using a GUI for a package management it's possible to easy enable or disable repositories and you can search for package groups like audio and video packages and install them all the same way a shell script would do that. Having such scripts you recommend to have, you're right that there will be no dependency conflicts because of the scripts, while I thought you were writing about packages that should install such groups and they will cause dependency conflicts. Anyhow it might be easier to install packages by a GUI for a package management. You can do it by a GUI the same way you can do it with shell scripts. Cheers, Ralf
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
