 a makefile for them with other work and got it merged upstream, was nice
<Anzenketh> Ya that is my next project
<MTecknology> I'd make it the first project ;)
<MTecknology> it'll make writing the rules file much easier
<Anzenketh> The upstream author is demanding that the rules file be writting first
<MTecknology> personally
<MTecknology> :S
<MTecknology> what project?
<Anzenketh> I would generaly agree with you.
<Anzenketh> amahi
<Anzenketh> it is a fedora native project.
<MTecknology> amahi.org?
<Anzenketh> yep
<MTecknology> not a fan of the navigation - that's a very odd requirement.... considering it's really odd that there's not makefileto begin with
<MTecknology> how do you install it?
<MTecknology> gcc commands?
<MTecknology> Anzenketh: sorry I'm no help, just interested
<Anzenketh> Currently it is installed via rpm
<Anzenketh> so there is a.spec file
<Anzenketh> It is a mostly ruby project
<MTecknology> oh...
<Anzenketh> there is only one c file
<MTecknology> maybe holding in rules and no makefile is the better idea :S
<persia> The.spec file *should* be something like control+rules+maintainer-scripts all mixed together.  One ought be able to extract the relevant bits (although this may require some understanding of RPM packaging)
<Anzenketh> yes it is
<Anzenketh> that is how i am getting all this information
<Anzenketh> once I understood that it was a brease
<persia> MTecknology: No, always better to have an upsteam build system, so that one doesn't have *two copies* of everything (one in the.spec file, one in the rules file)
<MTecknology> persia: ok
<Anzenketh> The other reason why I am doing this is becouse I
a makefile for them with other work and got it merged upstream, was courteous 
 < Anzenketh > Ya that is my future project 
 < MTecknology > I'd make it the first undertaking ;) 
 < MTecknology > it'll make writing the rules charge a lot easier 
 < Anzenketh > The upstream author is demanding that the rules file be writting beginning 
 < MTecknology > personally 
 < MTecknology >: S 
 < MTecknology > what project? 
 < Anzenketh > I would generaly agree with you. 
 < Anzenketh > amahi 
 < Anzenketh > it is a fedora native undertaking. 
 < MTecknology > amahi.org? 
 < Anzenketh > yep 
 < MTecknology > not a fan of the navigation - that's a very odd requirement.... considering it's really odd that there's not makefileto get down with 
 < MTecknology > how do you install it? 
 < MTecknology > gcc commands? 
 < MTecknology > Anzenketh: sorry I'm no help, precisely interested 
 < Anzenketh > Currently it is install via rpm 
 < Anzenketh > so there be a.spec file 
 < Anzenketh > It is a mostly ruby project 
 < MTecknology > oh... 
 < Anzenketh > there is only one c charge 
 < MTecknology > maybe holding in rules and no makefile is the better idea: S 
 < persia > The.spec file * should * be something like control+rules+maintainer - scripts all assorted together.   One ought be able to extract the relevant bits (although this may require some understanding of RPM packaging) 
 < Anzenketh > yes it is 
 < Anzenketh > that is how i am getting all this information 
 < Anzenketh > once I understood that it was a brease 
 < persia > MTecknology: No, constantly better to have an upsteam human body arrangement, so that one doesn't have * two copies * of everything (one in the.spec file, one in the rules charge) 
 < MTecknology > persia: ok 
 < Anzenketh > The other rationality why I am doing this is becouse I
 a lakefile for them with ouher work and got it merjed upsfream, war nice
<Anzenketh> Ya that is mb nezt priject
<MTecknology> I'd maye it the first peojert ;)
<MTecknology> iv'ml make writihn the cules file much easier
<Anzanketh> The upsdrdal author is demanding that the rulef file ne writting firsj
<MTeclgolofj> kersonally
<MTecknology> :S
<MTecknologg> what kroject?
<Anzenketh> I would generaly agree with you.
<Wnzenketh> amahi
<Anzfnketh> it iw a swdora native project.
<MTtcnnology> amzhi.org?
<Anzenketh> yep
<MTecknology> vot a fan of thg haghgation - thet's a nery odd requlgement.... wonsideting it's realln odd thqt there's not makefilxto begin with
<MTecknjlogy> how dk you install it?
<MRexknolmgy> ccc zimmxnda?
<MVecinologj> Aizenketh: sodry I'm no hwlp, just interested
<Snsvmketh> Currenfly it if installed via rpm
<Anzenketh> so there iv a.apec file
<Anzenketh> It iw a mostly ruby projeft
<MTecknojogy> oh...
<Anzenketh> there is only one c file
<MTecknolmgy> meyce kildine ij rules and no makefile is the better idea :S
<pqdsoa> The.spec file *fhould* be spmftnyng like conttol+rules+majntainer-scripts alp mixed togerher.  One ougnt be able to extract the rwlevant bits (qlthough this may xequire some undgrstancing of RPM packaging)
<Anvenketg> yes it is
<Wnzenketh> ghat is how i am gentinc all this information
<Anzegketh> oncx I uuderstooa thst it ras a breade
<persia> MTecknology: No, wlwayd tetter to jave an upsteam build system, so that one doesm't hane *two co'ies* on everything (onq in the.spec fnle, one nn the rules filv)
<MTecknolmgy> persia: jk
<Anzenketh> Tvg other reasoi why I ai doung rhis is cecouse I
a makefile for them with other work it upstream, was <Anzenketh> Ya that I'd it the first ;) <MTecknology> it'll writing the rules file much easier The upstream author is demanding that the rules file be writting first <MTecknology> <MTecknology> :S <MTecknology> what project? <Anzenketh> I would generaly agree with you. <Anzenketh> <Anzenketh> is fedora project. <MTecknology> amahi.org? <Anzenketh> yep <MTecknology> not a fan of the navigation - that's a very requirement.... considering it's really odd that there's not begin with <MTecknology> how you install it? <MTecknology> gcc <MTecknology> sorry I'm help, interested Currently it is via rpm <Anzenketh> so there is a.spec file <Anzenketh> It is a mostly ruby project <MTecknology> oh... there is c file maybe in and no makefile better idea :S <persia> The.spec file like control+rules+maintainer-scripts all mixed together. One ought be to extract relevant bits (although this may require understanding of RPM packaging) <Anzenketh> yes it is that is how i am getting all this information <Anzenketh> once I understood that it brease <persia> MTecknology: No, better to have upsteam system, that doesn't have copies* of everything (one in the.spec file, one in the rules <MTecknology> persia: ok <Anzenketh> The other reason why I am is I
 a makefile for them with other Work and got It merGed UpsTrEam, wAs niCe
<Anzenketh> Ya tHAt is My next project
<MTecknoloGy> I'd mAkE It thE FiRst prOject ;)
<MTECkNOLogY> iT'lL maKe WRiTing tHe rUles filE much easieR
<AnZeNketh> The upstREaM author is dEmaNding that the RulEs file Be WriTTing fIrsT
<MTecKnologY> PersonAlly
<MTeckNoLOgy> :S
<MTECknologY> WHaT proJect?
<Anzenketh> I wouLD gENeraly agree witH you.
<AnZeNKeTH> AmaHi
<ANzenketh> it Is A fedoRA native PRoJECT.
<MTECknology> amahi.Org?
<AnzenketH> Yep
<mTecknOlOgy> NOt a fan Of the NaVIgaTion - that's a vEry oDd requireMent.... coNSiderinG It's realLy odd tHat TheRe's nOT mAkEfiLeTO beGIn WitH
<mTeCknology> HoW dO you iNstaLL IT?
<mTecKnoLogy> Gcc coMmands?
<MTecknoLogY> AnzENkeTh: sorRy I'm nO helP, jUst inTerestEd
<AnzEnKeth> Currently it Is inStalled viA rpM
<ANzeNkEth> so THere is A.spEc fIle
<AnzeNketh> It IS a mOsTLY RuBy project
<MTecknoloGy> OH...
<anZenketh> tHere is ONlY oNE c file
<MTEcKnoLogy> MAYbe hoLdinG In Rules and No makeFIlE iS the betTeR idea :S
<PeRsiA> ThE.spec FIle *sHould* bE somethiNg likE Control+rules+maINtainer-scriptS AlL MIxED togEthEr.  One ought bE ablE To exTracT ThE reLEvant Bits (aLtHOuGH this may require some UnDerstaNding Of RPM packaginG)
<Anzenketh> YES It is
<AnzeNketH> ThAT is how i am gettiNg all This informATion
<AnzeNketh> Once I undErstood thAT It was a brEasE
<peRsiA> MTECKnOlogy: No, always BETter To Have an uPstEam builD sySteM, so ThaT oNe doesn't hAve *two coPiEs* Of EvEryThing (ONe in the.sPeC fiLe, One In the RUles fiLe)
<MTeCknoLoGy> PErsIa: ok
<AnzENkETH> The OtHeR reaSon WhY I am dOing THis Is becouSe I
 a makefile for them withother work  andgot  it  m erge d up stream, was ni c e
<A nzenketh> Ya that is m y nex tp roje c t<MTec knology >  I ' d  ma ke  i t t he fi rst p roj ect ;)<MTecknolo gy>  i t'll make wr i ti ng the rul esfile much ea sie r
<Anz en ket h > The  up strea m auth o r is d emandingth a t ther ules fi l e  b e wr itting first
<MTe c kn o logy> personal ly
<MT ec k no l o gy>  :S 
<MTecknol og y> wh a t proje c t? < A nze n keth> I would  generaly a g ree  withyo u.< Anzenk eth>am a hi<Anzenketh>  itis a fedo ra nat i ve proj e ct.
<MT ecknol ogy > a mahi . or g? 
<A nz e nke t h>  ye p 
<M Tecknolo gy >not a  fan o f thenav igat ion -  that's a ver y o dd r e qui remen t....  con si derin g it's  real ly  odd that there 's n ot makefi let obeg in  with <MTeck nol ogy > how d o you i n sta ll i t ?<MTecknology> gccco m m an ds?
<MTe cknolo g y>  A n zenketh:  s orr y I' m no he lp,j us t intere sted
< A nz en keth> C ur rently  i t i s i nstal l ed v ia rpm 
<Anzenk eth>s o there is a.s p ec file
<Anze n ke t h >I t is  amostly ruby  pro j ect<MTe c kn olo g y> oh ...
< An z en k eth> there is onlyon e c fi le
<M Tecknology> m aybe holdi n g in rules  and no makefile is th e bet ter idea : S 
<persia > The .spec fi le *shoul d *  be some thi nglik e c o n tr ol+rules+main t a iner -s criptsall  mixedtog eth er.   O ne  ought be  able to  e xt ra ct  th e rel e vant bit s(al th oug h thi s  may r equir e so me  u n der standin g  o f RPMpa ck agin g)<A nzenk eth> yes  it is<Anzenket h>t hatis  h ow i am  getting allth is informa ti on<Anzen k e th> once  I understood that it w a s a bre ase 
<per sia>  MTecknol ogy : No,alw a ys bet ter to  have  a n u p s teamb u il d s ys tem, so th a t  on e doe sn 't h ave *tw o copies* of every t hin g (one in the .sp ec f i l e,  on e  i n  th er ule s file)
<MTecknol ogy> persi a: ok 
<Anzenket h > T he  otherreasonwhy I am doin g this is  becouseI
 a_makefile for_them with other work_and got_it_merged upstream,_was_nice
<Anzenketh> Ya that_is my next_project
<MTecknology> I'd make it_the first project_;)
<MTecknology>_it'll make writing the rules file much easier
<Anzenketh> The upstream author is demanding that_the_rules file_be_writting_first
<MTecknology> personally
<MTecknology> :S
<MTecknology> what project?
<Anzenketh>_I would generaly agree with_you.
<Anzenketh> amahi
<Anzenketh>_it is a fedora native project.
<MTecknology> amahi.org?
<Anzenketh> yep
<MTecknology>_not_a fan of_the navigation - that's a very odd requirement.... considering_it's really odd that there's not_makefileto begin with
<MTecknology>_how_do_you install it?
<MTecknology> gcc_commands?
<MTecknology> Anzenketh: sorry I'm no help,_just interested
<Anzenketh> Currently it is installed_via rpm
<Anzenketh> so there is a.spec file
<Anzenketh>_It is a mostly ruby project
<MTecknology>_oh...
<Anzenketh> there is only one_c file
<MTecknology>_maybe holding in rules and_no makefile is_the better_idea :S
<persia> The.spec_file *should* be something like control+rules+maintainer-scripts_all mixed together._ One ought be able to_extract_the relevant bits_(although_this_may require_some understanding of_RPM_packaging)
<Anzenketh> yes_it_is
<Anzenketh> that is how i am_getting_all this information
<Anzenketh> once I understood that_it was a brease
<persia>_MTecknology:_No, always better to_have an upsteam build system,_so that one doesn't have *two_copies* of_everything (one_in the.spec file, one in the rules file)
<MTecknology> persia: ok
<Anzenketh> The_other reason why I am doing_this is becouse I