On Tue, Dec 29, 2009 at 11:38:11PM +0200, anatoly techtonik wrote: > On Tue, Dec 29, 2009 at 11:01 PM, W. Martin Borgert <deba...@debian.org> > wrote: > > Quoting "anatoly techtonik" <techto...@gmail.com>: > >> > >> python-support README [1] contains different instructions for > >> 'arch-all' and 'arch-any' packaged. How do I know which one is mine? > > > > all: Package works on all architectures without (re-) compilation, > > e.g. a program written in Python > > > > any: Package needs e.g. compilation, but will work on any > > architecture, e.g. a library for Python, but written in C > > Thanks! How about updating python-support README with these comments? > Something makes me think that most Python people who are the primary > readers of this text don't really know what is "arch-all" or > "arch-any".
People who are creating/maintaining packages should start by reading the general packaging documentation, which explains these. > > HTH! > > > > PS: debian-mentors is probably the best list for questions, that > > are not directly related to Python. > > You can't say it is not related to Python! And subscribing to yet > another mailing list is painful unless it is a Google Group. With all due respect, these are basic packaging terms that are not Python specific at all. regards, iustin -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
