Re: [microdc-devel] I: new version of microdc

[Steffen Schulz]

On 061128 at 15:20, Vladimir Chugunov wrote:
> there is a new version (0.15.0) of microdc2 available from
> http://corsair626.no-ip.org/microdc.
> This version includes:
> 
>     * Browsing remote users using XML filelists.
>     * Standalone tthsum utility to calculate TTH for specified files.
> 
>     * Number of fixes for bugs found in previous releases.

[...]
make[3]: Entering directory `/home/pepe/microdc2-0.15.0/src'
if gcc -DHAVE_CONFIG_H -I. -I. -I..  -I../lib -I../lib  -Wall -g -O2 -MT 
command.o -MD -MP -MF ".deps/command.Tpo" -c -o command.o command.c; \
then mv -f ".deps/command.Tpo" ".deps/command.Po"; else rm -f 
".deps/command.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I..  -I../lib -I../lib  -Wall -g -O2 -MT 
connection.o -MD -MP -MF ".deps/connection.Tpo" -c -o connection.o 
connection.c; \
then mv -f ".deps/connection.Tpo" ".deps/connection.Po"; else rm -f 
".deps/connection.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I..  -I../lib -I../lib  -Wall -g -O2 -MT 
variables.o -MD -MP -MF ".deps/variables.Tpo" -c -o variables.o variables.c; \
then mv -f ".deps/variables.Tpo" ".deps/variables.Po"; else rm -f 
".deps/variables.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I..  -I../lib -I../lib  -Wall -g -O2 -MT fs.o 
-MD -MP -MF ".deps/fs.Tpo" -c -o fs.o fs.c; \
then mv -f ".deps/fs.Tpo" ".deps/fs.Po"; else rm -f ".deps/fs.Tpo"; exit 1; fi
Makefile:404: *** Recursive variable `CFLAGS' references itself (eventually).  
Stop.
make[3]: Leaving directory `/home/pepe/microdc2-0.15.0/src'


I changed line 738 in src/Makefile:

-xml_flist.o: CFLAGS=$(CFLAGS) $(LIBXML2_CFLAGS)
+xml_flist.o: CFLAGS=$(LIBXML2_CFLAGS)

This may be amazingly stupid, I don't know, I'm not a programmer.
Works for me..


Feature-request: A bit more control about the file lists would be helpful. A
manual refresh-command, ability to "unshare" directories. Something like that.
I think "share" should work like the display variables.


What about the more open development process? I like mailing lists, but
a BTS would indeed be helpful. We can simply use ressources from sf.net
or similar sites. We already use the nongnu/microdc mailing list, maybe
they also provide a BTS. Or we can setup some stupid BTW software
ourselves(recommondations?). A simple wiki would do it, too...


regards,
pepe
-- 
       _----------------
 (o< ?-_    Less CO2    |  _o)                          +47/611-344-01
 //\    | for more ice! |  /\\  .o) .o)        gpg --recv-key A04D7875
 V_/_    ---------------  _\_V _(\)_(\)    mailto: address@hidden