Re: Inconsistency in source package naming for python modules
On 07/11/2013 04:07 AM, Piotr Ożarowski wrote:
> [Thomas Goirand, 2013-07-10]
>> And then, finally, it's called "migrate" instead of "sqlalchemy-migrate"
>> like upstream called it... :)
>> (this never happened to me with python-migrate, though that's a good
>> example of a IMO badly named source package)
>
> if you wanted to download python-migrate's sources... why didn't you
> tell apt-get that that's what you want?
> apt-get is clever enough to figure out the right source package name:
>
> $ apt-get source python-migrate
> [...]
> Picking 'migrate' as source package instead of 'python-migrate'
> [...]
Please don't pick on that specific example.
> `debcheckout python-migrate` will pick the right source package as well
debcheckout will use SVN, and I prefer git-svn.
Anyway, we're digressing. If you don't see a value in consistency, never
mind.
Thomas
Reply to: