From scott.jackson at enthought.com Tue Jun 26 19:57:40 2007 From: scott.jackson at enthought.com (Scott Jackson) Date: Tue, 26 Jun 2007 11:57:40 -0500 Subject: [Pisi] Pisi eggs Message-ID: <1182877060.20828.35.camel@stubbs> Hello all, We're attempting to use pisi in our build system, and we've been tiptoeing over modifications to the pisi source to avoid a fork. One thing in particular we've wanted to add is a way to have a consistent naming scheme across the eggs we create with pisi. At this time, we've called pythonmodules.egg() and grabbed/moved the file locations to a more consistent and descriptive naming scheme. For the record we're trying to get "-[.dev]--.egg". Is there a solid way to do this without modifying pythonmodules, or, would we be able to modify the egg() method and resubmit it to you? Thanks, Jackson From scott.jackson at enthought.com Tue Jun 26 20:42:41 2007 From: scott.jackson at enthought.com (Scott Jackson) Date: Tue, 26 Jun 2007 12:42:41 -0500 Subject: [Pisi] Pisi eggs In-Reply-To: <1182877060.20828.35.camel@stubbs> References: <1182877060.20828.35.camel@stubbs> Message-ID: <1182879761.20828.39.camel@stubbs> Oops, I wasn't aware that egg() was our method... So, we made a method to build eggs using pisi. :) The rest of the original message still holds true. Would pardus benefit from a method to create eggs from pisi? Thanks, Jackson On Tue, 2007-06-26 at 11:57 -0500, Scott Jackson wrote: > Hello all, > We're attempting to use pisi in our build system, and we've been > tiptoeing over modifications to the pisi source to avoid a fork. One > thing in particular we've wanted to add is a way to have a consistent > naming scheme across the eggs we create with pisi. At this time, we've > called pythonmodules.egg() and grabbed/moved the file locations to a > more consistent and descriptive naming scheme. For the record we're > trying to get "-[.dev]- version>-.egg". > Is there a solid way to do this without modifying pythonmodules, or, > would we be able to modify the egg() method and resubmit it to you? > Thanks, > Jackson > > _______________________________________________ > Pisi mailing list > Pisi at pardus.org.tr > http://liste.uludag.org.tr/mailman/listinfo/pisi > From caglar at pardus.org.tr Tue Jun 26 20:43:22 2007 From: caglar at pardus.org.tr (=?iso-8859-9?q?S=2E=C7a=F0lar?= Onur) Date: Tue, 26 Jun 2007 20:43:22 +0300 Subject: [Pisi] Pisi eggs In-Reply-To: <1182877060.20828.35.camel@stubbs> References: <1182877060.20828.35.camel@stubbs> Message-ID: <200706262043.24655.caglar@pardus.org.tr> 26 Haz 2007 Sal tarihinde, Scott Jackson şunları yazmıştı: > Hello all, > We're attempting to use pisi in our build system, and we've been > tiptoeing over modifications to the pisi source to avoid a fork. One > thing in particular we've wanted to add is a way to have a consistent > naming scheme across the eggs we create with pisi. At this time, we've > called pythonmodules.egg() and grabbed/moved the file locations to a > more consistent and descriptive naming scheme. For the record we're > trying to get "-[.dev]- version>-.egg". > Is there a solid way to do this without modifying pythonmodules, or, > would we be able to modify the egg() method and resubmit it to you? > Thanks, If i understand correctly what you want to achieve is the altering the name of the produced PiSi package with that format, please correct me if i'm wrong on this assumption. actionsAPI has no effect on package naming scheme used by PiSi. That scheme comes from package_name at util.py but i'm not sure changing that to another format causes any trouble because some other PiSi modules relay on that scheme also :(, but i don't think converting these functions to a much more generic ones is so hard to achieve. By the way please feel free to send any feedback/improvements/bug fixes/additions and etc. to list :) Cheers -- S.Çağlar Onur http://cekirdek.pardus.org.tr/~caglar/ Linux is like living in a teepee. No Windows, no Gates and an Apache in house! -------------- sonraki bölüm -------------- Yazı olmayan bir eklenti temizlendi... İsim: kullanılamıyor Tür: application/pgp-signature Boyut: 189 bayt Tanım: This is a digitally signed message part. Url: http://liste.pardus.org.tr/pisi/attachments/20070626/d882898f/attachment.pgp From ismail at pardus.org.tr Tue Jun 26 20:49:32 2007 From: ismail at pardus.org.tr (Ismail =?iso-8859-9?q?D=F6nmez?=) Date: Tue, 26 Jun 2007 20:49:32 +0300 Subject: [Pisi] Pisi eggs In-Reply-To: <1182879761.20828.39.camel@stubbs> References: <1182877060.20828.35.camel@stubbs> <1182879761.20828.39.camel@stubbs> Message-ID: <200706262049.36582.ismail@pardus.org.tr> On Tuesday 26 June 2007 20:42:41 Scott Jackson wrote: > Oops, I wasn't aware that egg() was our method... > So, we made a method to build eggs using pisi. :) > The rest of the original message still holds true. Would pardus benefit > from a method to create eggs from pisi? So you can install pisi packages without pisi installed on the system? Regards, ismail -- Perfect is the enemy of good -------------- sonraki bölüm -------------- Yazı olmayan bir eklenti temizlendi... İsim: kullanılamıyor Tür: application/pgp-signature Boyut: 827 bayt Tanım: This is a digitally signed message part. Url: http://liste.pardus.org.tr/pisi/attachments/20070626/e85dbd2c/attachment.pgp From faik at pardus.org.tr Tue Jun 26 20:56:05 2007 From: faik at pardus.org.tr (Faik Uygur) Date: Tue, 26 Jun 2007 20:56:05 +0300 Subject: [Pisi] Pisi eggs In-Reply-To: <1182877060.20828.35.camel@stubbs> References: <1182877060.20828.35.camel@stubbs> Message-ID: <200706262056.05179.faik@pardus.org.tr> On Tuesday 26 June 2007 19:57:40 Scott Jackson wrote: > Hello all, Hello, > We're attempting to use pisi in our build system, and we've been > tiptoeing over modifications to the pisi source to avoid a fork. Great. :) Hope you are using the uludag/branches/pisi-1.1 version... This is the stable branch of pisi. Cause trunk is not in a very dependable state right now. And lots of cleanups, and changes are going to be done to it. > One > thing in particular we've wanted to add is a way to have a consistent > naming scheme across the eggs we create with pisi. At this time, we've > called pythonmodules.egg() and grabbed/moved the file locations to a > more consistent and descriptive naming scheme. For the record we're > trying to get "-[.dev]- version>-.egg". Frankly, I do not have any experience with python eggs. I quickly read some info about them before writing this mail. So with your other mail, I understand that you are using the pisi's building mechanism to create an egg package and the outcome file is not going to be a pisi package as we know. - Faik