I need a bit more help from binary packaging people.

I have not heard from Darwin or BSD people for some time.  Is
your portfile up to date?  Do you have updates you want me to
include?  Have we introduced non-Linux non-GNU incompatibilities
lately that you want to see fixed and/or worked around?

For RPM, from my lack of RPM expertise (and RPM capable
environment until recently), I have not updated the "Prereq:"
field in git-core.spec.in at all.  I would appreciate somebody
to sanity check the list of dependencies.  The dependency list
Debian side has is more up-to-date and I am reasonably sure it
is accurate.  It lists patch, diff, and rcs (for the "merge"
command) as the essential dependency (aside from the shared
libraries like libc), and libmail-sendmail-perl, rsync, curl,
ssh, and libemail-valid-perl as the recommended dependency.  I
do not even know if RPM has the notion of such multi-tier
dependencies, but the latter list is meant to mean "you could
live without these, but to exercise this package fully you may
want them" (in our case of git-core, you could live without the
networking if you do not do multi-user, multi-repository).  If
RPM spec file has a way to say something like that, I would like
to see these packages (probably their names are different
between Debian and RPM) listed on the recommended dependency
list; otherwise I would want to see them added to the main
"Prereq:" list.

For Debian, we recommend lib*-*-perl packages.  Do we need to
recommend perl itself as well, or is it the case that things
that are covered with the automatic dependency chain need not be
listed?  Earlier I said that the Debian side is reasonably
accurate to the best of my knowledge, but I would appreciate it
if somebody ran lintian on it.

Pretty please?

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to