
I made a distutils command to take the Javascript files in an application and put them together and compress them. I'd like the result to kind of always be there; it would be distributed with the egg for instance. But I don't really want it in source control. So I think I need to make this part of the build somehow. What should I look for to do that? -- Ian Bicking | ianb@colorstudy.com | http://blog.ianbicking.org | Write code, do good | http://topp.openplans.org/careers

At 06:11 PM 4/20/2007 -0500, Ian Bicking wrote:
I made a distutils command to take the Javascript files in an application and put them together and compress them. I'd like the result to kind of always be there; it would be distributed with the egg for instance. But I don't really want it in source control. So I think I need to make this part of the build somehow. What should I look for to do that?
A couple of options: * Add it to MANIFEST.in, in which case it will be put in source distributions as well as the eggs, assuming it's in a package subdirectory and include_package_data is True * list it explicitly in package_data

Phillip J. Eby wrote:
At 06:11 PM 4/20/2007 -0500, Ian Bicking wrote:
I made a distutils command to take the Javascript files in an application and put them together and compress them. I'd like the result to kind of always be there; it would be distributed with the egg for instance. But I don't really want it in source control. So I think I need to make this part of the build somehow. What should I look for to do that?
A couple of options:
* Add it to MANIFEST.in, in which case it will be put in source distributions as well as the eggs, assuming it's in a package subdirectory and include_package_data is True
* list it explicitly in package_data
Is there a good way to ensure the files are created if necessary? I.e., if someone checks out the code (without these files) and runs setup.py install or develop, to make sure the compressing command is run? -- Ian Bicking | ianb@colorstudy.com | http://blog.ianbicking.org | Write code, do good | http://topp.openplans.org/careers

At 10:22 PM 4/22/2007 -0500, Ian Bicking wrote: >Phillip J. Eby wrote: >>At 06:11 PM 4/20/2007 -0500, Ian Bicking wrote: >>>I made a distutils command to take the Javascript files in an >>>application and put them together and compress them. I'd like the >>>result to kind of always be there; it would be distributed with the egg >>>for instance. But I don't really want it in source control. So I think >>>I need to make this part of the build somehow. What should I look for >>>to do that? >>A couple of options: >>* Add it to MANIFEST.in, in which case it will be put in source >>distributions as well as the eggs, assuming it's in a package >>subdirectory and include_package_data is True >>* list it explicitly in package_data > >Is there a good way to ensure the files are created if necessary? I.e., >if someone checks out the code (without these files) and runs setup.py >install or develop, to make sure the compressing command is run? You can subclass one of the build_* or install_* commands that would ordinarily be run.
participants (2)
-
Ian Bicking
-
Phillip J. Eby