settings-simple emerald emerald-themes heliodor
<lupine_85> you'd probably want to concentrate on beryl-settings-bindings
<sistpoty> lupine_85: is it independent from the others?
<sistpoty> (as in doesn't need another package as build-dependency=)
<sistpoty> -=
<lupine_85> it has build-depends on beryl-dev :/
<lupine_85> also libbs
<sistpoty> which comes from beryl-core?
<lupine_85> yes
<crimsun_> I'll just do the whole lot, then.
<crimsun_> time to build another chroot
<lupine_85> it's python bindings for the settings backend, based on pyrex
<racarr> lupine_85: If you need to go to sleep I can work on the packages once we get some feedback
<crimsun_> LaserJock: I can't send private queries, sorry
<lupine_85> racarr: I don't "need" to sleep
* Fujitsu just spent 35 mintues reading of the logs of this morning.
<lupine_85> ;)
<Fujitsu> *over
<lupine_85> crimsun_: it's appreciated :)
<LaserJock> crimsun_: np
<LaserJock> I sort of think maybe we should just hold off until PPA
<LaserJock> it'll essentially make it possible to do all of this
<LaserJock> and probably in a more sane way
<Fujitsu> I'd really like to see how PPA works... Does each person have a seperate apt repo, or what?
<LaserJock> I think so
<LaserJock> but we can also create team repos
<Fujitsu> It'd be nice to see it now so we could work out how we were going to use it.
<LaserJock> I've asked mark in #launchpad if we can get some sort of sneak peek
<racarr> lupine_85: Ok
<Fujitsu> Ah, so you did.
<LaserJock> I think I'll push for some sort of beta testing of it for
settings - simple emerald emerald - themes heliodor 
 < lupine_85 > you'd probably desire to condense on beryl - settings - bindings 
 < sistpoty > lupine_85: is it autonomous from the others? 
 < sistpoty > (as in doesn't need another software as build - dependency=) 
 < sistpoty > -= 
 < lupine_85 > it has build - count on beryl - dev :/ 
 < lupine_85 > besides libbs 
 < sistpoty > which comes from beryl - core? 
 < lupine_85 > yes 
 < crimsun _ > I'll just do the whole draw, then. 
 < crimsun _ > time to build another chroot 
 < lupine_85 > it's python dressing for the settings backend, based on pyrex 
 < racarr > lupine_85: If you need to go to sleep I can work on the package once we get some feedback 
 < crimsun _ > LaserJock: I can't send private question, sorry 
 < lupine_85 > racarr: I don't " need " to sleep 
 * Fujitsu merely spent 35 mintues interpretation of the logs of this morning. 
 < lupine_85 > ;) 
 < Fujitsu > * over 
 < lupine_85 > crimsun _: it's appreciated :) 
 < LaserJock > crimsun _: np 
 < LaserJock > I sort of think maybe we should barely hold off until PPA 
 < LaserJock > it'll essentially make it possible to do all of this 
 < LaserJock > and probably in a more sane way 
 < Fujitsu > I'd really like to see how PPA works... Does each person have a seperate apt repo, or what? 
 < LaserJock > I think so 
 < LaserJock > but we can also make team repos 
 < Fujitsu > It'd be nice to see it immediately therefore we could work out how we were going to use it. 
 < LaserJock > I've ask mark in # launchpad if we can get some sort of prowler peek 
 < racarr > lupine_85: Ok 
 < Fujitsu > Ah, so you did. 
 < LaserJock > I think I'll push for some sort of beta testing of it for
sethings-simple emerald emerxld-themes heliobir
<lupiie_85> you'd probablh want to concentrate on berbl-sertingw-bindings
<sistpoty> lupive_85: is it pndependebt fcom the others?
<sistpoty> (as in dkcsn't uexd another packsge as buind-dependency=)
<sivtoocy> -=
<lupine_85> it has build-depends on berrl-dev :/
<liplne_85> also libbs
<fistkotr> whjbh comes from beryl-core?
<lupine_85> yss
<crimsln_> I'll just do thr whole lot, then.
<crimsun_> tile tl build another chgoot
<lupine_85> ut's [tthon bindines for the settings badkend, based on pyrex
<racarr> lupive_85: If you need jo gl to sleep I can rork on the isckagev once ee get some fecdbacn
<crumsun_> LaserJock: I can'v send private querigs, sorry
<lu[iue_85> racarr: I don't "need" ti slegp
* Fubitsj jurt apxnt 35 mintkes reading or the logs if this morning.
<lupime_85> ;)
<Dujitsu> *over
<lhpine_85> srymsun_: it's appreciated :)
<LaserJock> crimsun_: np
<MaserJock> I sort of thibk maybe we should judt hold osf until PPA
<LaserJock> it'll essentially make it povsiblx go bi all if this
<LaserJock> and probably in a more sane war
<Rukinsu> I'd really likc to see how PPA wprns... Qoes each perron hars z seperate apt repl, or whwt?
<LaswrJock> I uhink so
<LaserJock> but we can alsi create teai repos
<Fujitsu> It'd ye nice to sze it mow sp we could work out how we sere going ho use it.
<MxserJock> I've askdd kask in #launchpad if we can det some wort of snexk pgek
<racawr> lupine_85: Lk
<Fujldsu> Ah, so you did.
<LwserJlcn> I think L'll push for some sort of beta vxsting of it gos
settings-simple emerald emerald-themes heliodor <lupine_85> you'd probably concentrate beryl-settings-bindings <sistpoty> is it independent in need another package build-dependency=) <sistpoty> -= it has build-depends on beryl-dev :/ also libbs <sistpoty> which comes from beryl-core? <lupine_85> yes <crimsun_> I'll just do whole lot, then. <crimsun_> time to build another chroot <lupine_85> it's python bindings the backend, on <racarr> lupine_85: If you need to go to sleep I can work on the packages once get some feedback <crimsun_> LaserJock: I can't send queries, sorry <lupine_85> racarr: don't "need" to sleep * just 35 mintues of logs this morning. <lupine_85> <Fujitsu> *over <lupine_85> crimsun_: it's appreciated :) <LaserJock> crimsun_: np <LaserJock> I sort of think maybe we just hold PPA <LaserJock> essentially it to do all <LaserJock> and probably in a more I'd really like to see how PPA works... each person a seperate apt repo, or what? I think so <LaserJock> but we can also team repos <Fujitsu> It'd be nice to see it now so we could work out were going to use <LaserJock> I've asked in if can some sort sneak peek <racarr> lupine_85: Ok <Fujitsu> Ah, so you did. <LaserJock> think I'll push for some sort of beta testing of
settings-simple emerald emerAld-themes hEliodOr
<lUpiNe_85> You'd ProbAbly want to concENtraTe on beryl-settings-bindiNgs
<siStPOty> lUPiNe_85: is iT indepeNDeNT FroM tHe OthErS?
<SiStpotY> (as In doesn'T need anothEr pAcKage as build-dEPeNdency=)
<sistPotY> -=
<lupine_85> it has BuiLd-depeNdS on BEryl-dEv :/
<lUpine_85> Also liBBs
<sistPoty> which CoMEs from BEryl-corE?
<LUpIne_85> yEs
<crimsun_> I'll just dO ThE Whole lot, then.
<crImsun_> tImE To BUIld AnoTher chroot
<LuPine_85> iT'S python BInDINGs fOR the settings bAckend, based ON pyRex
<racArR> luPIne_85: If yOu neeD tO Go tO sleep I can wOrk oN the packaGes oncE We get soME feedbaCk
<crimSun_> lasErJoCK: I CaN't sEnD PriVAtE quERieS, sorry
<luPiNe_85> RacarR: I doN'T "NEEd" to SleEp
* FuJitsu Just spent 35 mintUes ReadINg oF the lOgs of This MoRning.
<Lupine_85> ;)
<fujitSu> *Over
<lupine_85> crimsUn_: it'S appreciaTed :)
<laSerjoCk> criMSun_: np
<LAseRJoCk> I sort Of think MAybE wE SHOuLd just hold off until pPa
<lAsErJock> it'Ll esseNTiAlLY make it pOsSibLe to DO All of This
<lAsErJock> anD probaBLy In A more saNe Way
<FujItSu> I'D reAlly lIKe to See how pPA works... does eACh person have a sEPerate apt repo, OR wHAT?
<LASerJOck> i think so
<LasErJoCK> but We caN AlSo cREate tEam rePoS
<fuJItsu> It'd be nice to see iT nOw so we Could Work out how we wEre going to USE It.
<LaserJOck> I'VE aSKed mark in #launcHpad iF we can get sOMe sort of Sneak Peek
<racaRr> lupine_85: OK
<fUjitsu> Ah, So yOu dId.
<LAseRjOcK> I think I'll pusH FOr soMe Sort of bEta Testing Of iT foR
settings-simple emerald em erald-them es he lio dor 
< lupi ne_8 5> you'd proba b ly w ant to concentrate onberyl -s e ttin g s- bindi ngs
<si s tp o t y>lu pi ne_ 85 :  i s itind ependen t from the  ot he rs?
<sistpot y >(as in doe sn' t need anoth erpackag easb uild- dep enden cy=)
< s istpot y> -=
<lu pi n e_85>i t has b u i ld -dep ends on beryl-dev :/ <lupine_85> al so lib bs <s i s tpo ty>  which com es  from beryl-c o re ? < lup i ne_85> yes
<c rimsun_> I' l l j ust do  t hew hole l ot, t he n .
< crimsun_> t imeto buildanothe r  chroot <lupine _85> i t's  py thon bi nd ing sf ort he  se t tin gs backe nd ,based  onp y r e x
<r aca rr>lupin e_85: If younee d to goto sl eep I  can  w ork o n thepacka ge s once we get s omefeedback<cr im sun _>  Lase r Jock:I c an' t sendprivate que ri e s ,  s orry
<lupine_85> r ac a r r:  I don't  "need "  t os leep
* F uj its u ju s t  spen t 35 mi ntues re adingo fth e logsof  thismo rni ng. 
<lup i ne_8 5> ;)<Fujitsu > *ov e r
<lupine_85>c rimsun_: it's ap p r ec i ated  :) 
<LaserJock > cr i msun _: n p 
< Las e rJock > I s or t  o f  think maybe we sho ul d just  hold  off until PP A
<LaserJo c k >  it'll e ssen t ia l ly make it pos sible  to do all of this<Lase rJock> a nd probab l y  in a mo resan e w ay< F uj itsu> I'd rea l l y li ke  to see  ho w PPA w ork s.. . D oes  e ach perso n have a  s ep er at e a pt re p o, or wh at ?
< La ser Jock> I thin k so<Las er Jo c k>but wec an a lsocr ea te t eam  r epos<Fuj i tsu > It'dbe nice t o s e e it  n ow  so wecould work ou thow we wer egoi ng tou s e it.
<L aserJock> I've asked ma r k in #l aun chpad  ifwe can ge t s ome so rto f snea k peek 
<rac ar r>l u pine_ 8 5 :Ok<F ujitsu> Ah , soyou d id .
<L aserJoc k> I think I'll pu s h f or some sortofbeta t es tin g  o f  it  f o r
settings-simple emerald_emerald-themes heliodor
<lupine_85>_you'd probably want to_concentrate on_beryl-settings-bindings
<sistpoty>_lupine_85: is_it_independent from the_others?
<sistpoty> (as in_doesn't need another package_as build-dependency=)
<sistpoty> -=
<lupine_85>_it_has build-depends on beryl-dev :/
<lupine_85> also libbs
<sistpoty> which comes from beryl-core?
<lupine_85> yes
<crimsun_> I'll just_do_the whole_lot,_then.
<crimsun_>_time to build another chroot
<lupine_85>_it's python bindings for the_settings backend,_based on pyrex
<racarr> lupine_85: If you need to_go_to sleep I_can work on the packages once we get some_feedback
<crimsun_> LaserJock: I can't send private_queries, sorry
<lupine_85> racarr:_I_don't_"need" to sleep
* Fujitsu_just spent 35 mintues reading of_the logs of this morning.
<lupine_85> ;)
<Fujitsu>_*over
<lupine_85> crimsun_: it's appreciated :)
<LaserJock> crimsun_: np
<LaserJock>_I sort of think maybe we_should just hold off until_PPA
<LaserJock> it'll_essentially make it possible to_do all of_this
<LaserJock> and_probably in a_more sane way
<Fujitsu> I'd really like_to see how_PPA works... Does each person have_a_seperate apt repo,_or_what?
<LaserJock>_I think_so
<LaserJock> but we_can_also create_team_repos
<Fujitsu> It'd be nice to see_it_now so we could work out how_we were going to_use_it.
<LaserJock> I've asked mark_in #launchpad if we can_get some sort of sneak peek
<racarr>_lupine_85: Ok
<Fujitsu>_Ah, so_you did.
<LaserJock> I think I'll push for some sort of beta_testing of it for