(how do we know if packages we create work on other platforms?) That's the question, here's a bit of an explanation.
I create several packages...2 of which (horde-core and imp) are built for all since they are just html/php3 codes and not platform specific. But 2 others (rrdhcp and rrlogin) are not. I build them on i386 systems and have no clue (other than the author saying they "should" work on other platforms) whether they will compile/work on say m68k, hurd, sparc platforms. So...I upload them under a "any" clause, the m68k,sparc,etc ppl suck them up, compile them on their systems and.... (?) . Do they test them out or do they just upload them into the distribution and wait to see if anyone who uses them finds problems in them? If there is a problem, who is responsible for fixing it? (ie,) if say rrlogind has problems on sparc systems, who handles this? if it were i386 it would be me in conjunction with the author, but since I don't have access to a sparc debian system I can only assume it's not me but rather the person who is doing the porting. Are my conclusions pretty much correct? Is there a way for me to have access to debian (sparc/hurd/m68k/etc...) systems to do porting on so that this responsibility layes with me? Thanks Ivan =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Ivan E. Moore II Rev. Krusty http://snowcrash.tdyc.com [EMAIL PROTECTED] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- GPG KeyID=0E1A75E3 GPG Fingerprint=3291 F65F 01C9 A4EC DD46 C6AB FBBC D7FF 0E1A 75E3 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
