
I'm new to setuptools and I'm hoping to have a few questions answered. I also have some observations that may be useful, but that can come later.
1. why does setuptools bdist_rpm use --single-version-externally-managed?
2. is it possible to have setuptools write dependency information not just to requires.txt but also to setup.cfg so that RPM will be aware of the dependencies?
3. This is more of a distutils question, but, what can be done about the INSTALLED_FILES containing directories that aren't marked with %dir (this causes two problems: /all/ directories end up being created but NOT owned by the RPM, and all files /under/ that directory get included, which means they likely get included *twice* to to also being explicitly included).
Sorry for the multi-issue email, I'm new at this.

At 11:11 AM 12/8/2006 -0600, Jon Nelson wrote:
I'm new to setuptools and I'm hoping to have a few questions answered. I also have some observations that may be useful, but that can come later.
- why does setuptools bdist_rpm use --single-version-externally-managed?
To avoid the need for .pth files, mainly.
- is it possible to have setuptools write dependency information not
just to requires.txt but also to setup.cfg so that RPM will be aware of the dependencies?
Not really, but you could create a custom egg_info writer that will reconfigure the bdist_rpm command at runtime based on that information. See the setuptools documentation for more about egg-info writers. You'll need some understanding of the distutils command framework to do this effectively.
- This is more of a distutils question, but, what can be done about the
INSTALLED_FILES containing directories that aren't marked with %dir (this causes two problems: /all/ directories end up being created but NOT owned by the RPM, and all files /under/ that directory get included, which means they likely get included *twice* to to also being explicitly included).
Sorry, no clue on that one.
participants (2)
-
Jon Nelson
-
Phillip J. Eby