Debian packaging documentation for Python packages (was: How do I know if my package is 'arch-all' or 'arch-any'?)

2009-12-30 Thread Ben Finney
anatoly techtonik writes: > I do not argue. I just want to say that for people with Python > background this information should be structured in different manner > omitting various irrelevant and confusing details. If you feel that should be done, you're welcome to devote resources to help it ha

Re: How do I know if my package is 'arch-all' or 'arch-any'?

2009-12-30 Thread anatoly techtonik
>> On Tue, Dec 29, 2009 at 11:48 PM, Iustin Pop wrote: >> > >> > People who are creating/maintaining packages should start by reading >> > the general packaging documentation, which explains these. >> >> Python package maintainers do not need to learn all that irrelevant C >> stuff they have no id

Re: How do I know if my package is 'arch-all' or 'arch-any'?

2009-12-30 Thread Josselin Mouette
Le mardi 29 décembre 2009 à 23:38 +0200, anatoly techtonik a écrit : > > 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

Re: How do I know if my package is 'arch-all' or 'arch-any'?

2009-12-30 Thread Ben Finney
anatoly techtonik writes: > On Tue, Dec 29, 2009 at 11:48 PM, Iustin Pop wrote: > > > > People who are creating/maintaining packages should start by reading > > the general packaging documentation, which explains these. > > Python package maintainers do not need to learn all that irrelevant C >

Re: How do I know if my package is 'arch-all' or 'arch-any'?

2009-12-30 Thread anatoly techtonik
On Tue, Dec 29, 2009 at 11:48 PM, Iustin Pop wrote: > > People who are creating/maintaining packages should start by reading the > general packaging documentation, which explains these. Python package maintainers do not need to learn all that irrelevant C stuff they have no idea about. They need