I think splitting into amule, amule-daemon, amule-gui, amule-utils and amule-utils-gui amule-linkshandler is better:
amule is the monolithic app amule-daemon is, well, the daemon amule-gui, guess what? amule-gui amule-linkshandler would be the ed2k-links-handler amule-utils would be all console utils: webserver amulecmd cas alcc amule-utils-gui would be all gui utils: webserverDLG amulecmdDLG wxcas alc This is because people using amule-dameon might not want to have to install libwxgtk+libgtk+xlib just to be able to install amuleweb ;) About the ed2k links handler, it should be in a separate package so that it can be used for all amule-daemon, amule-gui and amule, not having the need to install all otehr console utils. Obviusoly, the best would be to have aseparate package for each, but i don't think you are in the mood for that ;) C'ya soda! > I think that the slitting is actually not complete. I'm aware of that. > But I don't have enough time, and I will take my new appartment in a > week, so, I will have more time in a few days. > I think the best thing is : > - one package amule-utils, which is actually the same as the current > - one package amule-webserver which contains webserver for amule > - one package amule-daemon which contains only the daemon > - one package amule which contains the complete GUI > > But I don't know if I can make a such split. I will test as soon as > possible. It's may be possible to package a new package called > amule-data to put .po files and other data like icons, ... This > decision needs test and I will do it as soon as possible. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
