<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.5.6"> </HEAD> <BODY> <BLOCKQUOTE TYPE=CITE> <PRE> I wasn't sure, I figured it was best to mark them as documentation anyway, but that's easily remedied. Not including any documentation means the package doesn't own the doc dir and it doesn't get removed with the rest of the files, however. Would adding a '%dir % {_datadir}/blablah' be approriate? That seems a little kludgy. </PRE> </BLOCKQUOTE> I'm pretty sure the %{_datadir}/doc/%{name}-%{version} ownership is handled by rpm within the %doc tag <BLOCKQUOTE TYPE=CITE> <PRE> Sure, the quixote RPMS should be up shortly (just making sure they work on my x86_64 machine at home as they aren't noarch). I don't currently package durus, but will look into it. If it's as easy to package as most python libraries, I don't imagine it will take very long. </PRE> </BLOCKQUOTE> good. thanks. <BLOCKQUOTE TYPE=CITE> <PRE> The package naming guidelines page doesn't specify a name format for python modules, but I'm assuming the convention is similar to that for perl modules? i.e. python-${source_name} </PRE> </BLOCKQUOTE> yes they do: <A HREF="http://fedoraproject.org/wiki/PackageNamingGuidelines#head-bb4665ea46aa0653710ab594efb3207a94eda636">http://fedoraproject.org/wiki/PackageNamingGuidelines#head-bb4665ea46aa0653710ab594efb3207a94eda636</A> Submit your CLA and stuff as described here: <A HREF="http://fedoraproject.org/wiki/Extras/CvsAccess">http://fedoraproject.org/wiki/Extras/CvsAccess</A> and cc me on the emails. thanks! -sv </BODY> </HTML>