> > The latex2html issue is easy -- we should check to see whether the
> > latex2html binary exists, otherwise skip it.
>
> No, that's not correct.
>
> Even if the latex2html binary exists, you can't call it. non-free things
> could be installed on the build host, but as long as you don't call them,
> you don't depend on them.
>
> There should be some kind of configure-like setup.
I'm sorry, I don't quite see the distinction here. I'm not particularly
familiar with Debian policy - does being able to take advantage of non-free
software that happens to be present constitute a dependency?
> debian/changelog changes with each upload(version, changelog entry, and
> timestamp).
>
> Don't get me wrong, I am not trying to keep the debian stuff to myself.
> It's just difficult to integrate with upstream(any upstream, not just xen).
OK, makes sense. If it's going to cause trouble, perhaps you could maintain
the Debian build system for the "real" packages separately but supply
snapshots to check in every so often? I agree it's not really ideal.
Cheers,
Mark
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Home