Jakub Wilk escreveu isso aí:
> * Antonio Terceiro , 2012-01-25, 10:12:
> >Another argument in favor of using the same name for source and
> >binary packages: suppose there is "libfoo", and independent
> >bindings for Perl, Python and Ruby, all called "foo", and that
> >"foo" is unique in their resp
* Antonio Terceiro , 2012-01-25, 10:12:
Another argument in favor of using the same name for source and binary
packages: suppose there is "libfoo", and independent bindings for Perl,
Python and Ruby, all called "foo", and that "foo" is unique in their
respective upstream language-specific names
Don Armstrong escreveu isso aí:
> On Mon, 23 Jan 2012, Jakub Wilk wrote:
> > I normally advocate using upstream name for source package name
> > (even if it's a single binary package and the binary package would
> > have a different name due to $LANGUAGE policy).
>
> If you are only building one b
On Mon, 23 Jan 2012, Jakub Wilk wrote:
> I normally advocate using upstream name for source package name
> (even if it's a single binary package and the binary package would
> have a different name due to $LANGUAGE policy).
If you are only building one binary package, the source package should
hav
Jakub Wilk writes:
> I normally advocate using upstream name for source package name (even if
> it's a single binary package and the binary package would have a
> different name due to $LANGUAGE policy).
This can make things unnecessarily awkward and confusing for, say, the
BTS. Nothing that pe
* Russ Allbery , 2012-01-23, 13:30:
python-futures for the package name, surely, no?
do you mean the binary? that will be python-concurrent.futures, as per
python policy; for the source I'm open to comments
I was thinking of the source. If you're building a single binary
package from the sourc
Sandro Tosi writes:
> On Mon, Jan 23, 2012 at 22:06, Russ Allbery wrote:
>> python-futures for the package name, surely, no?
> do you mean the binary? that will be python-concurrent.futures, as per
> python policy; for the source I'm open to comments
I was thinking of the source. If you're bu
On Mon, Jan 23, 2012 at 22:06, Russ Allbery wrote:
> python-futures for the package name, surely, no?
do you mean the binary? that will be python-concurrent.futures, as per
python policy; for the source I'm open to comments
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: ht
Sandro Tosi writes:
> * Package name: futures
> Version : 2.1.2
> Upstream Author : Alex Grönholm
> * URL : http://pypi.python.org/pypi/futures
> * License : BSD
> Programming Lang: Python
> Description : backport of concurrent.futures package from Pyt
Package: wnpp
Severity: wishlist
Owner: Sandro Tosi
* Package name: futures
Version : 2.1.2
Upstream Author : Alex Grönholm
* URL : http://pypi.python.org/pypi/futures
* License : BSD
Programming Lang: Python
Description : backport of concurrent.future
10 matches
Mail list logo
