The Testing Area :: June Extensions
More extensions now posted:
Thanks to Curaga for:
busyserver.tar.gz
Thanks to WDef for:
loopaes-3.1f-2.4.31_x86.dsl
loopaes-3.1f-2.4.26knpx_x86.dsl
gpgpatched.dsl
Thanks to J.S. for:
python2.5.uci
Download from the testing area.
Be sure to read the info file.
I would like to split 'amule-gtk1.uci' into 2 parts:
1. amule.uci (amule, alc, alcc, ed2k, wxcas) - about 850K
2. amule-utils.uci (amule daemon, amule command-line client, amule remote gui) - about 2M
3. The 2 pkgs above depend on separate 'libwxgtk1.dsl' which is ready now. Also preparing more wxgtk1 apps, namely 'xchm' and 'wxdfast'.
Or should I use 'amule-gtk1.uci' and 'amule-gtk1-utils.uci'?
jls_legalize, you already have a package called 'amule-gtk2-2.1.3-ver2.dsl', so I thought I had better ask here first before changing the name. Another reason is, I think it is better to consult developers first.
Thanks everybody.
stupid_idiot: The one thing that sounds odd about that plan is the fact that you want to make *.uci packages that depend on a *.dsl package. One of the main points about using UCIs is that they do not require the filesystem to be opened any further to writing, as *.dsl extensions do. By requiring the *.dsl, you remove this important feature of uci packages.
Yes, you are right. The size of libwxgtk1 seems more suitable for uci/unc:
4904 /usr/local/lib/libwx_gtk-2.6.so.0
Reason for choosing .dsl was because I'd like to have it in a standard libdir (/usr/local/lib) and for simplicity. uci is okay as well by placing a symlink in /usr/local/lib to the file in /opt/libwxgtk1. But since uci should not have files outside /opt I think a unc is more suitable. What do you think?
p.s. If it is not difficult to make a unc, could anyone please post a short description of the process? Thank you very much.
stupid_idiot: you can set LD_LIBRARY_PATH, using a wrapper script. Since it's pretty small, you may as well include it in amule.uci (which I assume amule-utils will be dependent on)
Next Page...
original here.