--- El dom, 14/3/10, Michelle Konzack <[email protected]> escribió:
> Hello Miri, > > I asume you are not electronic engineer or something > simiar, so please > make 'piklab-prog' into a -common package and the 'piklab' > KDE gui into > an optional one. I am an electronic engineer, in fact. Anyway, I'm not using piklab for anything at the moment. > Me and a bunch others on my mailinlists coding on the > commandline and we > are very anoyes about installing 185 MByte ok KDE-Libs, fam > and such. I'll have a look at that as soon as I find some spare time for it. > Also KDE does not work with FAM and AVAHI deactivated where > FA crash my > Workstation on each startup and AVAHI screw up my network. > > OK, my suggestion would be, make following packages: > > 1) piklab (this > include the KDE gui) > 2) piklab-common (only the console program) Maybe piklab-bin or piklab-cli would be more appropriate, but it is not a bad idea. > and let "piklab" depend on "piklab-common" so > users can install the > commandline tool without bothred with a full disk of > KDE libs on the > console... > > Note: My current Devel-Station is a TI Sitara AM3517 where > I have only > 2 GByte of NAND Flash and 256 MByte of > DDR2, so having unneccesary > KDE installed is not very nice by > Debian Maintainers/Developers. > > Oh, -- and plase take attention, it seems, while compiling > 'piklab-prog' > it liks to KDE libe even if they are not used. Can > you check thie? Yup, I'll look into that as soon as I find some spare time to upgrade the package. Thanks, Miry -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
