Re: Bug#728797: ITP: python-mne -- Python modules for MEG and EEG data analysis

[Alexandre Gramfort <alexandre.gramfort@m4x.org>]

hi Andreas,

I've pushed a new tag v0.7rc5

all PRs have now been merged and the release should happen tomorrow.

Can you just confirm that we're good on the debian side? I'd love to avoid
a hot fix tomorrow due to a problem with debian packaging :)

yaroslav : I've updated the github debian branch so you can give it a try too.

thanks again for all your help

Alex


On Mon, Nov 25, 2013 at 9:47 AM, Alexandre Gramfort
<alexandre.gramfort@m4x.org> wrote:
> hi Andreas,
>
>> Well, having a target in debian/rules is not sufficient.  You could even
>> put a target "take_over_world_domination" and finally nothing will
>> happen if you have no rule that depends from this target. :-)
>
> indeed :)
>
>> I just merged this target into override_dh_installman and now it is
>> used.
>
> thanks
>
>> BTW, I need to insist on my naming question which finally becomes quite
>> abstruse if you call the source package mne-python but the binary
>> python-mne.  Please answer my question (now asked in the third flavour
>> of rewording) why exactly you are specifying the used programming
>> language in the package name.
>
> well mne-python is a python library and all the other python packages I use
> on a daily basis start with python- e.g. python-sklearn, python-numpy,
> python-scipy. The convention seem to be python-"import name" and mne-python
> is imported in python with "import mne" hence the package name "python-mne"
>
> does it make sense?
>
> Best,
> Alex