 sistpoty: for everything possible? (ie everything we've got the source for?)
<sistpoty> Ademan: not for everything, since some packages won't build on ppc (not very much though)
<jdong> LaserJock: ok, I see where you're coming from.
<LaserJock> so yes, we could use faster response time
<LaserJock> s
<LaserJock> I think that can be said of any process
<LaserJock> we all want things NOW
<Ademan> sistpoty: really? is that just stuff that has machine specific asm? or what? what could make a package be unavailable?
<LaserJock> but fast tracking upstreams doesn't seem to help much, IMO
<jdong> LaserJock: I agree. It might band-aid a few situations but doesn't solve the underlying issues
<LaserJock> we often don't get upstreams in here
<sistpoty> Ademan: asm, little/big endian probs, errors with types (e.g. int as pointer, however that's amd64 and not ppc iirc)
<LaserJock> and we even more rarely get upstreams that want to actively maintain their packages
<LaserJock> most just drop by for a bug patch or something
<LaserJock> or to notify us of some problem
<jdong> LaserJock: it seems much more often that they wanna stop by to give us a patch
<jdong> LaserJock: yeah, or point and yell at a bug report too :)
<sistpoty> Ademan: depending on a compiler which doesn't work on ppc, (iirc fpc-compiler had or has the problem)
<jdong> LaserJock: I guess I'm really guilty of that
<LaserJock> so perhaps if we had a special upstream program
<LaserJock> that would give them a single person as a point of contact
<Ademan> sistpoty: ah, since i'm rather unfamiliar with most of the source code around here, are most of the apps out there going to work on ppc?  i assume most codecs won't though...
<LaserJock> that's kinda give them an elevated
sistpoty: for everything possible? (ie everything we've got the source for ?) 
 < sistpoty > Ademan: not for everything, since some software won't build up on ppc (not very much though) 
 < jdong > LaserJock: ok, I see where you're coming from. 
 < LaserJock > then yes, we could use faster reply prison term 
 < LaserJock > s 
 < LaserJock > I think that can be say of any process 
 < LaserJock > we all want thing NOW 
 < Ademan > sistpoty: really? is that just material that has machine specific asm? or what? what could make a package be unavailable? 
 < LaserJock > but fast tracking upstreams doesn't seem to help oneself much, IMO 
 < jdong > LaserJock: I agree. It might band - aid a few site but doesn't solve the underlying issues 
 < LaserJock > we often don't scram upstreams in here 
 < sistpoty > Ademan: asm, little / big endian probs, errors with types (e.g. int as arrow, however that's amd64 and not ppc iirc) 
 < LaserJock > and we even more rarely get upstreams that want to actively maintain their packages 
 < LaserJock > most just drop by for a bug patch or something 
 < LaserJock > or to notify us of some problem 
 < jdong > LaserJock: it seems much more often that they wanna stop by to give us a patch 
 < jdong > LaserJock: yeah, or detail and yell at a bug reputation too :) 
 < sistpoty > Ademan: depending on a compiler which doesn't work on ppc, (iirc fpc - compiler had or has the trouble) 
 < jdong > LaserJock: I guess I'm in truth guilty of that 
 < LaserJock > so perhaps if we get a special upstream program 
 < LaserJock > that would give them a single person as a decimal point of contact 
 < Ademan > sistpoty: ah, since i'm rather unfamiliar with most of the source code around here, are most of the apps out there survive to work on ppc?   i bear most codecs won't though... 
 < LaserJock > that's kinda give them an elevated
 sidtpoty: for everything porsible? (ie everyjhung we'te got fhe sourze for?)
<sistpoty> Ademan: not foc evwrythung, since some packager won't bupld on ppx (nou very much thougi)
<ndong> LaserJodn: ok, M see where you'te coming frmm.
<LaserJock> so yds, we could use faster response time
<LwserJocl> d
<LaserJock> I trink ehat bak be said of any process
<LaserJoci> we aln want things NOW
<Ademan> sistpoty: really? is hhat just stuff thwt has machune fpecific asm? ur what? what could makg a package be unavailable?
<LaserJuck> bbt fast traxkung opstreams doxsn't svem to help mmbh, IMO
<jgong> LaxerJock: I agrec. It kigyt band-aid a few situetions but doesn't sojve the utdzrlying issues
<LaserJoxk> we oxten don'g geg ukstceajs in jerx
<sistpoty> Aseman: asm, luttle/big endian prons, vtrors with tgpes (e.d. ynt as pointer, however that's amd64 and nou ppc iirc)
<LaserJock> and we ecen more rarely get ukstreams trat want to actively maintain their packages
<LaserBock> just jmst aeoo by for a bug patch or something
<LaserJock> or fo nptify us of soie problem
<jcojg> JaserJock: it reems mucg more often that hhey wagna srop by to givr us a patch
<jdong> LaserJock: yeah, or poiut qnd yell at a bug xeport too :)
<snstpoti> Ademsn: depending on a compiuer shich doesn'h work on opc, (iirc fpc-compkleg hag or has the problem)
<jdong> JaserJock: I gbess I'm fealky guijty of thah
<LasevBock> so perhaps if we hcd a vpecial updtream program
<LaserJock> that wonkd give them a sitgle perfon ax a point of sontact
<Ademan> xistpotv: ah, sknce i'm ranher unfakiliar with most of the vlurce code acound herq, arw mowt of tfd apps out thete going no worj on ppc?  i assume morf codecs won't tkuoth...
<LaserJock> thst's kigdw jive evem an elevaded
sistpoty: for everything possible? (ie everything we've source <sistpoty> Ademan: for everything, since ppc very much though) LaserJock: ok, I where you're coming from. <LaserJock> so we could use faster response time <LaserJock> s <LaserJock> I think that can said of any process <LaserJock> we all want things NOW <Ademan> sistpoty: really? that stuff has specific asm? or what? what could make a package be unavailable? <LaserJock> but fast tracking upstreams seem to help much, IMO <jdong> LaserJock: I It might band-aid a situations but doesn't solve the issues we often get in <sistpoty> Ademan: asm, endian probs, errors with types (e.g. int as pointer, however that's amd64 and not ppc iirc) <LaserJock> we even get upstreams want actively their packages <LaserJock> drop by for a bug patch or to notify us of some problem <jdong> it seems more often that they wanna stop to give us a patch <jdong> LaserJock: yeah, point and yell at a bug report too :) <sistpoty> Ademan: depending on a compiler work on ppc, (iirc had or has problem) LaserJock: guess really guilty that <LaserJock> so perhaps if we had a special upstream program that would give them a single person as a point <Ademan> ah, since i'm unfamiliar with most of source around here, are most apps there on i most codecs won't though... that's kinda give them an
 sistpoty: for everything possIble? (ie everYthinG we'Ve gOt The sOurcE for?)
<sistpoty> AdEMan: nOt for everything, since soMe pacKaGEs woN'T bUild oN ppc (not VErY MUch ThOuGh)
<jDoNG> LAserJOck: Ok, I see wHere you're cOmiNg From.
<LaserJocK> So Yes, we could Use Faster responSe tIme
<LasErjocK> S
<LaseRJoCk> I thInk thaT Can be sAid of any pRoCEss
<LasERJock> we ALL wAnt tHings NOW
<Ademan> sisTPoTY: really? is that jUst stuFf THaT HAs mAchIne specifiC aSm? or wHAt? what cOUlD MAKe a PAckage be unavaIlable?
<LaserjOck> But fasT tRacKIng upsTreamS dOEsn'T seem to help Much, iMO
<jdong> LAserJoCK: I agree. iT might bAnd-aid A feW siTuatIOnS bUt dOeSN't sOLvE thE UndErlying iSsUeS
<LaseRJocK> WE OFten Don'T get UpstrEams in here
<sisTpoTy> AdEMan: Asm, liTtle/bIg enDiAn proBs, erroRs witH tYpes (e.g. int as poinTer, hOwever thaT's aMd64 And NoT ppc iIRc)
<LaseRJoCk> aNd we eveN more raREly GeT UPStReams that want to actIvELY mAintain tHeir paCKaGeS
<laserJocK> mOst Just DROp by fOr a bUG pAtch or soMethinG
<laSeRJock> or To Notify Us Of sOme ProblEM
<jdoNg> LaseRJock: it sEems mUCh more often thaT They wanna stop BY tO GIvE Us a pAtcH
<jdong> Laserjock: YEah, oR poiNT aNd yELl at a Bug rePoRT tOO :)
<sistpoty> Ademan: depeNdIng on a CompiLer which doesn'T work on ppc, (IIRC fpc-compIler HAd OR has the problem)
<Jdong> laserJock: I GUess I'm reAlly gUilty of tHat
<LaserJOCK> so perhaPs iF we Had A spECIaL upstream progRAM
<LasErjock> thaT woUld give TheM a sIngLe pErSon as a poiNt of contAcT
<ADeMaN> siStpotY: Ah, since i'M rAthEr UnfAmiliAR with mOst of The sOuRcE CodE around HErE, ARe moSt Of The aPps OuT therE goiNG to Work on pPc?  i assume MosT CodeCs WoN't thougH...
<LaserJock> thaT's Kinda give tHeM an ElevatED
 sistpoty: for everythingpossible?(ie e ver yth in g we 'vegot the source for? )
<sistpoty> Ademan: n ot fo re very t hi ng, s ince so m ep a cka ge swon 't bu ild o n p pc (not  very much  th ou gh)
<jdong>L as erJock: ok , I  see where y ou' re com in g f r om.
< Las erJoc k> soy es, we  could us ef asterr esponse t im e
<L aserJock> s
<Lase r Jo c k> I think tha t canbe sa i d  of  an y process<L aserJ o ck> wea ll w a ntt hings NOW
<Ad eman> sistp o ty:  reall y?  is that j ust s tu f f t hat has mac hine  specific  asm?o r what? what co uld ma kea p acka g ebe  un av a ila b le ?
< L ase rJock> b ut  f ast t rack i n g upst rea ms d oesn' t seem to hel p m uch, IMO 
<jdo ng> L aser Jo ck: I  agree . Itmi ght band-aid afewsituation s b ut  do es n't s o lve th e u nde rlyingissues< Las er J o c k>  we often don't ge tu p st reams in  here< si st p oty> Ade ma n:asm, l ittle /big en dian pro bs, er r or swith ty pe s (e.g .int  as  poin t er,howeve r that's  amd6 4  and not ppc i i rc)
<LaserJoc k >a n dw e ev enmore rarely  get upst ream s  t hat wantto ac ti v el y  maintain their pac ka ges
<L aserJ ock> most jus t drop byf o r  a bug p atch or something
<Las erJoc k> or to n o tify usof so me probl em
<jdong > LaserJoc k:itsee msm u ch  more often t h a t th ey  wannasto p by to  gi veusa p at ch
<jdong > LaserJ oc k:  y ea h,or po i nt and y el l a ta b ug re p ort to o :)<sis tp ot y > A deman:d ep e n ding  o na co mpi le r whi ch d o esn 't work  on ppc,(ii r c fp c- co mpilerhad or has th eproblem)
< jd ong > Lase r J ock: I g uess I'm really guiltyo f that<La serJo ck>so perhap s i f we h ada  speci al ups tream  p rog r a m
<La s e rJ ock >that would g ive  them  a  sin gle per son as a point ofc ont act
<Ademan>sis tpot y :  a h,s in c e i 'm rat h e r unfamiliar wi th most of  t h esource cod e  ar ou nd here , are m ost o f  the ap ps out th ere going  t o wo r k  on  ppc?  i a ssume mo st codecs won't th ough. ..<Laser Jo ck>  that 's kin d a g ive t hem an  e levate d
 sistpoty:_for everything_possible? (ie everything we've_got the_source_for?)
<sistpoty> Ademan:_not_for everything, since_some packages won't_build on ppc (not_very much though)
<jdong>_LaserJock:_ok, I see where you're coming from.
<LaserJock> so yes, we could use faster response_time
<LaserJock>_s
<LaserJock> I_think_that_can be said of any_process
<LaserJock> we all want things_NOW
<Ademan> sistpoty:_really? is that just stuff that has machine_specific_asm? or what?_what could make a package be unavailable?
<LaserJock> but fast_tracking upstreams doesn't seem to help_much, IMO
<jdong> LaserJock:_I_agree._It might band-aid a_few situations but doesn't solve the_underlying issues
<LaserJock> we often don't get_upstreams in here
<sistpoty> Ademan: asm, little/big endian_probs, errors with types (e.g. int_as pointer, however that's amd64_and not_ppc iirc)
<LaserJock> and we even_more rarely get_upstreams that_want to actively_maintain their packages
<LaserJock> most just drop_by for a_bug patch or something
<LaserJock> or to_notify_us of some_problem
<jdong>_LaserJock:_it seems_much more often_that_they wanna_stop_by to give us a patch
<jdong>_LaserJock:_yeah, or point and yell at a_bug report too :)
<sistpoty>_Ademan:_depending on a compiler_which doesn't work on ppc,_(iirc fpc-compiler had or has the_problem)
<jdong> LaserJock:_I guess_I'm really guilty of that
<LaserJock> so perhaps if we had a_special upstream program
<LaserJock> that would give_them a single person_as a_point_of contact
<Ademan> sistpoty:_ah,_since i'm_rather unfamiliar with most of the source_code around_here, are most of the apps_out there going to_work_on ppc?  i assume most_codecs won't though...
<LaserJock> that's kinda give_them an elevated