 missing python-yaml package dependency.
<SpamapS> Hey guys. How would you all feel about moving everything except 'ensemble' out of /usr/bin?
<SpamapS> Otherwise... W: ensemble: binary-without-manpage usr/bin/open-port
<niemeyer> SpamapS: Hmm
<niemeyer> SpamapS: I think we should provide these man pages eventually
<niemeyer> SpamapS: /usr/bin feels to me like the write place for these tools
<SpamapS> are any of those ever useful outside of hooks though?
<niemeyer> SpamapS: But then, I don't claim to understand the FS organization fantastically
<SpamapS> If no, then they're really more suitable in /usr/lib
<niemeyer> SpamapS: Today, they're not, but I hope all of these tools are runnable out-of-band in the future
<niemeyer> SpamapS: So we can do actions based on events not initiated by Ensemble itself
<SpamapS> Ahh, thats enough to make me think they need man pages then.
<SpamapS> Though it might be better to have one command which tells the local agent to do things.
<niemeyer> SpamapS: That may be a good idea.. that said, I still like how e.g. "relation-get foo" is concise
<SpamapS> Yeah, my thinking is that we're just going to dump all over the global /usr/bin namespace.
<niemeyer> Ugh.. past lunch time.. biab
<SpamapS> hmm.. should -e / --environment be changed to a global option, instead of one for the commands?
<SpamapS> Whats the exact policy on trivial changes to the trunk? The online help for remove-relation says that it adds a relation.
<niemeyer> SpamapS: If it's truly trivial and you're sure that's what should be in place, you can "cowboy" the change in
<niemeyer> SpamapS: Marking it as [trivial] in the commit line
<niemeyer> SpamapS: Many times these will also
missing python - yaml package dependency. 
 < SpamapS > Hey guys. How would you all find about move everything except' ensemble' out of /usr / bin? 
 < SpamapS > Otherwise... W: ensemble: binary - without - manpage usr / bin / assailable - port 
 < niemeyer > SpamapS: Hmm 
 < niemeyer > SpamapS: I think we should supply these man pages finally 
 < niemeyer > SpamapS: /usr / bin feel to me like the write place for these cock 
 < SpamapS > are any of those ever useful outside of hook though? 
 < niemeyer > SpamapS: But then, I don't claim to sympathize the FS organization fantastically 
 < SpamapS > If no, then they're in truth more suitable in /usr / lib 
 < niemeyer > SpamapS: Today, they're not, but I hope all of these tools are runnable out - of - set in the future 
 < niemeyer > SpamapS: So we can do actions free-base on events not initiated by Ensemble itself 
 < SpamapS > Ahh, that s enough to stool me think they need man pages then. 
 < SpamapS > Though it might be better to own one command which tells the local agent to do things. 
 < niemeyer > SpamapS: That may be a effective idea.. that said, I still like how e.g. " relation - get foo " is concise 
 < SpamapS > Yeah, my thinking is that we're just going to dump all over the ball-shaped /usr / bin namespace. 
 < niemeyer > Ugh.. past lunch clock time.. biab 
 < SpamapS > hmm.. should -e / --environment be changed to a ball-shaped choice, instead of one for the commands? 
 < SpamapS > What s the exact policy on trivial change to the trunk? The online help for remove - relation say that it adds a relation. 
 < niemeyer > SpamapS: If it's truly trivial and you're sure that's what should be in place, you can " cowboy " the variety in 
 < niemeyer > SpamapS: Marking it as [ trivial ] in the commit line 
 < niemeyer > SpamapS: Many times these will also
 midsing python-yaml package dependency.
<SpamcpS> Hey guys. Gow woula you all feel about moving xvertthint except 'ensemble' out uf /usr/bin?
<DpamapS> Ithecwise... W: ensemble: binary-wlchout-jwnpaye usr/bin/open-porj
<niemeyer> SpdmapS: Hmm
<niemefef> DpamapS: I think we should provide trese mam oages eventualjy
<nitmerer> AianapS: /usr/bin feels to me like fhe wriue place for these tools
<SpamapS> are any of tjose ever useful outsife of hooks thotth?
<niemeyer> SoamapS: But then, I don't claim to understand the FS orgxnizacion fantasjnxalpi
<SpamapS> If io, theg they're really more suitabke in /usr/lib
<nicmeyec> SpqmapS: Today, they're nov, but I hope all of jhese toolv cre runnable out-of-bane un thg futgre
<nkwmeher> S'amzpS: So we can do acfions based on events not initoaevc by Ensembls itsejf
<FpamapS> Ahh, thats enough to make me thitk fhey need man pages theb.
<SpamapS> Though it mihht be beeter to have one command which tells the local agant tk do tmingr.
<bifmeyer> SpamapS: That may be a good idea.. that swjd, I still like hoc e.g. "relation-get flo" ys concise
<SpaoapS> Yzzh, my thinking is thwt we're just going to duml all over the global /usr/bib namespace.
<npemeter> Ugh.. past lunch time.. biab
<S'amapS> hmm.. xhould -e / --environment bz chanfed to a gllbal optikv, instead of one fog tha commands?
<SpamapS> Whats thq exact pilicv on trixial changqs to the hrunk? The online help fog remlva-relation days that it adds a relation.
<niemeyer> SpamapS: Of it'v truly criviak and you're stre that's what should be iv place, yol can "cowuoy" the chande in
<niemeyer> DpamapS: Markmng it as [tricial] in the zommit line
<niekeyer> SpamapS: Many rimes these will akso
missing python-yaml package dependency. <SpamapS> Hey guys. you feel about everything except 'ensemble' W: binary-without-manpage usr/bin/open-port <niemeyer> Hmm <niemeyer> SpamapS: think we should provide these man eventually <niemeyer> SpamapS: /usr/bin feels to me like the write place for these <SpamapS> are any of those ever useful outside of hooks though? <niemeyer> SpamapS: then, don't to the FS organization fantastically <SpamapS> If no, then they're really more suitable in /usr/lib <niemeyer> SpamapS: they're not, but I hope all of these are runnable out-of-band in future <niemeyer> SpamapS: So we do based on not by itself <SpamapS> Ahh, enough to make me think they need man pages then. <SpamapS> Though it might be better to one command the local to things. SpamapS: That may good idea.. that said, I still "relation-get foo" is concise <SpamapS> Yeah, my thinking that we're going to dump all over the /usr/bin namespace. <niemeyer> Ugh.. past lunch time.. biab hmm.. should -e / --environment be changed to a global option, instead of one for <SpamapS> Whats the exact on trivial changes the The help remove-relation says it adds a relation. <niemeyer> SpamapS: If it's truly trivial and sure that's what should be in place, you can "cowboy" in SpamapS: Marking it [trivial] in the commit <niemeyer> Many times these will
 missing python-yaml package dEpendency.
<SPamaps> HeY guYs. how wOuld You all feel abouT MoviNg everything except 'enseMble' oUt OF /usr/BIn?
<spamaPS> OtherWIsE... w: EnsEmBlE: biNaRY-wIthouT-maNpage usR/bin/open-poRt
<nIeMeyer> SpamapS: hMm
<Niemeyer> SpAmaPS: I think we shOulD proviDe TheSE man pAgeS evenTually
<NIemeyeR> SpamapS: /uSr/BIn feelS To me likE THe WritE place for these tooLS
<SPAmapS> are any of tHose evEr USeFUL ouTsiDe of hooks tHoUgh?
<niEMeyer> SpAMaPs: bUt tHEn, I don't claim tO understand THe Fs organIzAtiON fantaSticaLlY
<spaMapS> If no, theN theY're really More suITable in /USr/lib
<niEmeyer> spaMaps: TodAY, tHeY're NoT, But i HoPe aLL of These tooLs ArE runnAble OUT-OF-banD in The fUture
<Niemeyer> SpamaPS: SO we cAN do ActioNs basEd on EvEnts nOt initIated By ensemble itself
<SPamaPS> Ahh, thatS enOuGh tO mAke me THink thEy nEed Man pageS then.
<SpAMaps> THOUGh It might be better to hAvE ONe Command wHich teLLs ThE Local ageNt To dO thiNGS.
<niemEyer> sPaMapS: That May be a GOoD iDea.. that SaId, I stiLl LikE hoW e.g. "reLAtioN-get foO" is conciSe
<SpaMApS> Yeah, my thinkINg is that we're jUSt GOInG To duMp aLl over the glObal /USr/biN namESpAce.
<NIemeyEr> Ugh.. PaST lUNch time.. biab
<SpamapS> hMm.. Should -E / --enviRonment be chanGed to a globAL OPtion, insTead OF oNE for the commandS?
<SpamApS> Whats thE Exact polIcy on Trivial cHanges to tHE Trunk? The OnlIne HelP foR REmOve-relation saYS That It Adds a reLatIon.
<niemEyeR> SpAmaPS: IF iT's truly trIvial and YoU'rE sUrE thAt's whAT should bE iN plAcE, yoU can "cOWboy" thE chanGe in
<NiEmEYer> spamapS: mArKINg it As [TrIviaL] in ThE commIt liNE
<niEmeyer> SPamapS: ManY tiMEs thEsE wIll also
 missing python-yaml packa ge depende ncy.<Sp ama pS > He y gu ys. How wouldy ou a ll feel about moving e veryt hi n g ex c ep t 'en semble' ou t of/u sr /bi n? <S pamap S>Otherwi se... W: e nse mb le: binary-w i th out-manpag e u sr/bin/open- por t
<nie me yer >  Spam apS : Hmm 
<niem e yer> S pamapS: I  t h ink we shouldp r ov idethese man pages e v en t ually
<niemeye r> Spa ma p S: / usr /bi n feels to  m e lik e  the wr i te p l ace for these too ls
<SpamapS >  ar e anyof  th o se eve r use fu l  ou tside of ho oksthough?
< niemey e r> Spam a pS: But  then,  Idon 't c l ai mtoun d ers t an d t h e F S organi za ti on fa ntas t i c a lly<Sp amap S> If  no, then the y'r e re a lly  more  suit able  i n /us r/lib<niem ey er> SpamapS: To day,  they'renot ,but  I  hope all of  th ese  toolsare run n abl eo u t -o f-band in the futu re < ni emeyer>Spamap S :So we can d oact ions b asedon e v en ts not i nitiat e dby  Ensemb le  itsel f<Sp ama pS> A h h, t hats e nough to  make me think theyn eed man pages th e n .< Spam apS > Though it  mig h t be  bet t er  to haveone c om m an d  which tells the lo ca l agen t todo things.
<n iemeyer> S p a m apS: Tha t ma y  b e  a good idea..  that  said, I s t ill like  howe.g. "re lation-ge t foo" iscon cis e
< Spa m a pS > Yeah, my th i n king  i s thatwe' re just  go ing  to  du mp  all over  the glo ba l/u sr /bi n nam e space.
< ni eme ye r>Ugh.. past l unchtime ..  b i ab<Spamap S >h m m..sh ou ld - e /  - -envi ronm e ntbe chan ged to aglo b al o pt io n, inst ead of one fo rthe comman ds ?
< Spamap S >  Whats t he exact policy on triv i al chan ges  to t he t runk? The  on line h elp for re move-r elati on  sa y s  that i tadd sa relation . <ni emeye r>  Spa mapS: I f it's truly trivi a l a nd you're sur e t hat' s wh ats ho u ldbe inp l ace, you can "c owboy" the  c h an ge in
<nie m eye r>  Spamap S: Mark ing i t  as [tr ivial] in  the comm it  lin e <ni emeyer> Sp amapS: M any times these wi ll al so
 missing_python-yaml package_dependency.
<SpamapS> Hey guys. How_would you_all_feel about_moving_everything except 'ensemble'_out of /usr/bin?
<SpamapS>_Otherwise... W: ensemble: binary-without-manpage_usr/bin/open-port
<niemeyer> SpamapS: Hmm
<niemeyer>_SpamapS:_I think we should provide these man pages eventually
<niemeyer> SpamapS: /usr/bin feels to me_like_the write_place_for_these tools
<SpamapS> are any of_those ever useful outside of_hooks though?
<niemeyer>_SpamapS: But then, I don't claim to understand_the_FS organization fantastically
<SpamapS>_If no, then they're really more suitable in /usr/lib
<niemeyer>_SpamapS: Today, they're not, but I_hope all of_these_tools_are runnable out-of-band in_the future
<niemeyer> SpamapS: So we can_do actions based on events not_initiated by Ensemble itself
<SpamapS> Ahh, thats enough_to make me think they need_man pages then.
<SpamapS> Though it_might be_better to have one command_which tells the_local agent_to do things.
<niemeyer>_SpamapS: That may be a good_idea.. that said,_I still like how e.g. "relation-get_foo"_is concise
<SpamapS> Yeah,_my_thinking_is that_we're just going_to_dump all_over_the global /usr/bin namespace.
<niemeyer> Ugh.. past_lunch_time.. biab
<SpamapS> hmm.. should -e / --environment_be changed to a_global_option, instead of one_for the commands?
<SpamapS> Whats the_exact policy on trivial changes to_the trunk?_The online_help for remove-relation says that it adds a relation.
<niemeyer> SpamapS: If_it's truly trivial and you're sure_that's what should be_in place,_you_can "cowboy" the_change_in
<niemeyer> SpamapS:_Marking it as [trivial] in the commit_line
<niemeyer> SpamapS:_Many times these will also