On Fri, Aug 13, 2010 at 07:51:37PM +0200, Miroslav Suchý wrote:
>
> My approach is not optimal as we populate it with those generic
> names. But one step in time.
It's not one step in time. There won't be other steps to fix it
properly in the future. And if there will be, it will just be
twice as much change, twice as much potential breakage and
twice as much work.
> We can even conflict with some others packages on really generic names like:
> common/apache.py
> Which is good. Becouse you will get at least error during
> installation.
No you won't, unless you will be testing Spacewalk with the full
OS (including EPEL) installations. And it will not prevent conflicts
in the future because people adding packages to EPEL will know
nothing about these filenames used by Spacewalk packages.
> >instead and change all the relevant imports to have the "rhn."
> >prefix? Alternatively we could have /usr/share/rhn to be a symlink
> >to %{python_sitelib}/rhn or something similar.
>
> That's ugly. Since we have there other data which should not be
> stored in %{python_sitelib}
> E.g. RHN-GPG-KEY, RHNS-CA-CERT
You can always do the symlinks for the subdirectories, can't you?
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
