ubuntu-packaging if you get stuck.
<muelli> persia: thx. will have a look
<muelli> heh. funky rules file -.- And the best thing: It (nearly) does what I want! holy cow!
<persia> muelli: Are you using python-support?  There should be a built-in dh_pysupport call if you are.
<shadeslayer> so... is there someone here who can update me with the latest 3.0 format?
<shadeslayer> like point me to a doc..
<muelli> persia: Sorry. I don't know whether I'm using "python-support". I started from scratch calling setup.py myself from the debian/rules, but I thought it was wrong. So I tried cdbs which messed installation up and now I'm using your rules.tiny.
<persia> muelli: Add python-support to Build-Depends: in debian/control
<muelli> persia: k. right now I put debhelper, cdbs, python-setuptools and python-central. But I will get rid of cdbs and python-central in favour of python-support, I guess.
<muelli> persia: btw: shall we move this to #ubuntu-packaging? :)
<persia> Even odds.  If you're planning to push this package into the main repos for lucid+1, it's equally on-topic in either place.
<muelli> persia: k :)
<muelli> oh, and I wouldn't mind pushing that but for now I only want to distribute that program easily using the great PPA system :) But I'm willing to do the right^tm steps so that the package is ready for inclusion. And would keep spending my time caring about it.
<persia> For PPA stuff, #ubuntu-packaging is more on-topic : this channel is about working on Ubuntu directly
<Anzenketh> persia: Thanks for your help I think i convinced him to change to cmake in the future for a packaging system.
<Anzenketh> but right now he wants to do it this way
<persia> Anzenketh: That's fine.  In my experience the best way to get someone to change their code is to patch it to do it the way
ubuntu - packaging if you get stuck. 
 < muelli > persia: thx. will have a look 
 < muelli > heh. fetid rule file -.- And the best matter: It (nearly) do what I want! holy cow! 
 < persia > muelli: Are you using python - documentation?   There should be a built - in dh_pysupport call if you are. 
 < shadeslayer > thus... is there someone here who can update me with the latest 3.0 format? 
 < shadeslayer > like point me to a doc.. 
 < muelli > persia: Sorry. I don't sleep together whether I'm using " python - support ". I start from scribble calling setup.py myself from the debian / rules, but I thought it was wrong. So I try on cdbs which messed installation up and now I'm use your rules.tiny. 
 < persia > muelli: Add python - support to Build - Depends: in debian / control 
 < muelli > persia: k. right now I frame debhelper, cdbs, python - setuptools and python - central. But I will get rid of cdbs and python - central in favour of python - support, I think. 
 < muelli > persia: btw: shall we move this to # ubuntu - packaging? :) 
 < persia > Even odds.   If you're planning to push this package into the main repos for lucid+1, it's equally on - topic in either place. 
 < muelli > persia: k :) 
 < muelli > oh, and I wouldn't mind pushing that but for now I only want to distribute that program easily use the great PPA system :) But I'm uncoerced to cause the right^tm footfall so that the package is ready for inclusion body. And would keep spend my time caring about it. 
 < persia > For PPA material, # ubuntu - packaging is more on - topic: this channel is about working on Ubuntu directly 
 < Anzenketh > persia: Thanks for your help I think i convinced him to change to cmake in the future for a packaging system. 
 < Anzenketh > but right nowadays he wants to suffice it this way 
 < persia > Anzenketh: That's fine.   In my experience the best way to get someone to transfer their code is to patch it to do it the way
ubujtu-packaging if you get rtuck.
<muelli> persia: thx. will gave a luok
<muelli> heh. funky rules fipe -.- And the best thing: It (neafly) does ahat I wqnt! ioly cow!
<persia> mnslli: Arc you msing 'ython-support?  Jhere should be a built-in gh_oydupport call if you are.
<shadeslayer> fo... is tnege someone herg who san hidcte me with the latest 3.0 format?
<sgadeslajer> like point me to a doc..
<muelli> persia: Sorgy. I don't know whether I'm using "pifhog-wupport". I stxrted from scratch calming setup.py myself from the decian/rbles, but I jkiugjj it was wroig. So P tried cdbs which mevsed inxtallation up snd noq I'm using your rules.viny.
<persia> muelli: Adq python-sgp'ort to Build-Depends: un debidn/cottrou
<nueuli> pxrsja: k. rlghv now I put debhelper, xdbs, python-setuptooks qnd python-cenfral. Btt I will get rid of cdbs and python-centrdl jn favour of python-suppirt, I guess.
<muelli> perdia: btw: srall we move this to #ubuntu-packaging? :)
<persia> Even mdds.  Kf viu're ooajning to push this package into the main repof fpr lucid+1, it's equclly on-topic in rihhrt place.
<muelli> kersia: k :)
<mhelli> oh, and I woupdn't migd puwhing thau but for now I only want to disrribute that program easily usiug the great PPA systrm :) But I'm willing to du ths right^tm sheps so tgxt the package ir rvady for inclusion. And would kqep spendmng mv time cxrinb aboue it.
<persia> For I[A stuff, #ubuntu-pacnaginy is kore on-toplc : this channel is about workiij on Ubuntu doractny
<Anzenkzth> pevsia: Thanks for your help I tkink i cjnvinzed him to change to cmake ig the future xlr a packagiig system.
<Wnzebkety> but rkeht now he wanys to do pt thiw way
<persia> Anzenkcth: Tfzt's fine.  In my exkeeience the besy wxy eo gxt soiaone to chance tfeif code is to kctcm ig to do it the way
ubuntu-packaging if you get stuck. <muelli> persia: have look <muelli> funky rules file It does what I holy cow! <persia> Are you using python-support? There should a built-in dh_pysupport call if you are. <shadeslayer> so... is there someone here can update me with the latest 3.0 format? <shadeslayer> like point me to doc.. persia: I know whether I'm using "python-support". I started from scratch calling setup.py myself from the debian/rules, but thought it was wrong. So I tried cdbs messed installation up and I'm using your rules.tiny. <persia> Add to Build-Depends: debian/control persia: right now I debhelper, cdbs, python-setuptools and python-central. But I will get rid of cdbs and python-central in favour of I guess. btw: shall move to :) <persia> Even you're planning to push this package repos for lucid+1, it's equally on-topic in either <muelli> persia: :) <muelli> oh, and I wouldn't pushing that but for now I only want distribute that program easily using the great PPA system :) But I'm willing to do steps so that the is ready for And keep my caring about <persia> For PPA stuff, #ubuntu-packaging is more on-topic : this channel about working on Ubuntu directly <Anzenketh> persia: Thanks for your think convinced him to to cmake in the for packaging system. <Anzenketh> but he to way Anzenketh: fine. In my experience best way to get someone change their code is it the way
ubuntu-packaging if you get stUck.
<muelli> pErsia: Thx. WilL hAve a Look
<Muelli> heh. funky RUles File -.- And the best thing: It (nEarly) DoES whaT i wAnt! hoLy cow!
<peRSiA> MUelLi: arE yoU uSInG pythOn-sUpport?  THere should Be a BuIlt-in dh_pysupPOrT call if you Are.
<Shadeslayer> sO... is There sOmEonE Here wHo cAn updAte me wITh the lAtest 3.0 formAt?
<SHadeslAYer> like POInT me tO a doc..
<muelli> persia: sOrRY. I don't know whetHer I'm uSiNG "pYTHon-SupPort". I startEd From sCRatch caLLiNG SEtuP.Py myself from tHe debian/rulES, buT I thouGhT it WAs wronG. So I tRiED cdBs which messEd inStallatioN up and NOw I'm usiNG your ruLes.tinY.
<peRsiA> mueLLi: adD pyThON-suPPoRt tO buiLd-DependS: iN dEbian/ContROL
<MUellI> peRsia: K. righT now I put debheLpeR, cdbS, PytHon-seTuptoOls aNd PythoN-centrAl. But i wIll get rid of cdbs And pYthon-centRal In FavOuR of pyTHon-supPorT, I gUess.
<mueLli> persIA: btW: sHALL wE move this to #ubuntu-pAcKAGiNg? :)
<persia> even odDS.  IF yOU're plannInG to Push THIs pacKage INtO the main Repos fOR lUcId+1, it's eqUaLly on-tOpIc iN eiTher pLAce.
<mUelli> pErsia: k :)
<muElli> oH, And I wouldn't minD Pushing that buT FoR NOw i Only WanT to distribuTe thAT proGram EAsIly USing tHe greAt ppA SYstem :) But I'm willing to Do The rigHt^tm sTeps so that the Package is rEADY for inclUsioN. anD Would keep spendIng my Time caring ABout it.
<peRsia> FOr PPA stuFf, #ubuntu-pACKaging is MorE on-TopIc : tHIS cHannel is about WORkinG oN Ubuntu DirEctly
<AnZenKetH> peRsiA: THanks for yOur help I ThInK i CoNviNced hIM to changE tO cmAkE in The fuTUre for A packAginG sYsTEm.
<ANzenketH> BuT RIght NoW hE wanTs tO dO it thIs waY
<PerSia> AnzeNketh: That'S fiNE.  In mY eXpErience The best way to gEt Someone to cHaNge Their cODE is to patCh it to do it the way
ubuntu-packaging if you ge t stuck.
< muell i>per si a: t hx.will have a lo o k
<m uelli> heh. funky rule s fil e- .- A n dthe b est thi n g: I t ( ne ar ly)  d o es  what  Iwant! h oly cow!
< per si a> muelli: A r eyou usingpyt hon-support?   T here s ho uld be abui lt-in  dh_py s upport  call ifyo u  are.< shadesl a y er > so ... is there some o ne here who can u pdateme wi t h  th e l atest 3.0fo rmat? <shades l ay e r >  li k e point me to  a doc..
<m u ell i> per si a:S orry.I don 't kno w whether I 'm u sing "pyt hon-su p port".I  starte d from  sc rat ch c a ll in g s et u p.p y  m yse l f f rom thede bi an/ru les, b u t  I t hou ghtit wa s wrong. So I  tr iedc dbs  whic h mes sedin stall ationup an dnow I'm using y ourrules.tin y.<p ers ia > mue l li: Ad d p yth on-supp ort toB uil d- D e p en ds: in debian/cont ro l <m uelli> p ersia: k.  r i ght nowIput  deb h e lper,  cdb s ,python-s etupto o ls  a nd pyth on -centr al . B utI wil l  get  rid o f cdbs a nd py t hon-central in favour of pyt h on - s up p ort,  Iguess.
<mue lli> pers ia:b tw : s h all w e mov et hi s  to #ubuntu-packagi ng ? :)
< persi a> Even odds.   If you'r e p lanningto p u sh this package i nto t he main re p os for l ucid+ 1, it'sequally o n - topic in  ei the r p lac e . 
< muelli> persi a :  k : )<muelli > o h, andI w oul dn' t m in d pushing  that bu tfo rno w I  only want todi str ib ute  that progra m eas ilyus in g  th e great PP A syst em  : ) Bu t I 'm  will ingt o d o the r ight^tm s tep s  soth at  the pa ckage is read yfor inclus io n.And wo u l d keep s pending my time caringa bout it .
< persi a> F or PPA st uff , #ubu ntu - packag ing is  more  o n-t o p ic :t h is  ch an nel is abo u t  wo rking  o n Ub untu di rectly
<Anzenketh> per sia: Thanks f oryour h el p I th i nkic onv i n ced him to chan ge to cmak ei nthe future for  a  packag ing sys tem.< Anzenke th> but r ight nowhe  wan t s  to  do it thi s way
<p ersia> An z enket h :That' s f ine. In  my  expe rience the  best  way t oget so meone  t o change  their code is to patch  it to  do i t t he way
ubuntu-packaging if_you get_stuck.
<muelli> persia: thx. will_have a_look
<muelli>_heh. funky_rules_file -.- And_the best thing:_It (nearly) does what_I want! holy_cow!
<persia>_muelli: Are you using python-support?  There should be a built-in dh_pysupport call if_you_are.
<shadeslayer> so..._is_there_someone here who can update_me with the latest 3.0_format?
<shadeslayer> like_point me to a doc..
<muelli> persia: Sorry. I_don't_know whether I'm_using "python-support". I started from scratch calling setup.py myself_from the debian/rules, but I thought_it was wrong._So_I_tried cdbs which messed_installation up and now I'm using_your rules.tiny.
<persia> muelli: Add python-support to_Build-Depends: in debian/control
<muelli> persia: k. right now_I put debhelper, cdbs, python-setuptools and_python-central. But I will get_rid of_cdbs and python-central in favour_of python-support, I_guess.
<muelli> persia:_btw: shall we_move this to #ubuntu-packaging? :)
<persia> Even_odds.  If_you're planning to push this package_into_the main repos_for_lucid+1,_it's equally_on-topic in either_place.
<muelli>_persia: k_:)
<muelli>_oh, and I wouldn't mind pushing_that_but for now I only want to_distribute that program easily_using_the great PPA system_:) But I'm willing to_do the right^tm steps so that_the package_is ready_for inclusion. And would keep spending my time caring about it.
<persia>_For PPA stuff, #ubuntu-packaging is more_on-topic : this channel_is about_working_on Ubuntu directly
<Anzenketh>_persia:_Thanks for_your help I think i convinced him_to change_to cmake in the future for_a packaging system.
<Anzenketh> but_right_now he wants to do it_this way
<persia> Anzenketh: That's fine. _In my experience the best_way_to_get someone to change their_code is to patch it to_do it the_way