> > In addition, there were questions raised about the name "repozo.py".
> > Surely there is a clearer name for this utility.
>
> Yes, I suggested zodb-fsbackup.
If that's what it does ;-)
(I've never had any idea what repozo.py does...)
> I've never stated that they were in the way of the package being
> accepted, and in fact made it clear that it was "not critical" and that
> the practice was merely "discouraged".
Cool, so lets have the .py's stay then :-)
> I'm having second thoughts about this being a viable solution. I don't
> see what the difference is between renaming something in /usr/bin and
> removing it. Existing users who access /usr/bin/fs* are going to
> experience breakage either way. May as well rename.
> > In addition, there were questions raised about the name "repozo.py".
> > Surely there is a clearer name for this utility.
>
> Yes, I suggested zodb-fsbackup.
If that's what it does ;-)
(I've never had any idea what repozo.py does...)
> I've never stated that they were in the way of the package being
> accepted, and in fact made it clear that it was "not critical" and that
> the practice was merely "discouraged".
Cool, so lets have the .py's stay then :-)
> I'm having second thoughts about this being a viable solution. I don't
> see what the difference is between renaming something in /usr/bin and
> removing it. Existing users who access /usr/bin/fs* are going to
> experience breakage either way. May as well rename.
Yep, +1 from me :-)