new version python3

[Daniel Echeverry]

Hi mentors

I am working in a new version of lfm, the new version is python3 for
this reason I want to know if necessary create a ITP bug with a new
package like this lfm3, to package this new version, or if I could
continue with the same package.

regards

-- 
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
Linux user: #477840
Debian user
Software libre

Re: new version python3

[Gianfranco Costamagna]

Hi,

>I am working in a new version of lfm, the new version is python3 for
>this reason I want to know if necessary create a ITP bug with a new
>package like this lfm3, to package this new version, or if I could
>continue with the same package.


the question is:

is this something that the average normal use will notice or care about?
e.g. if the user experience won't change, and the upstream development has 
moved to python3 only
seems legit to just switch the dependencies.

Moreover nowadays both are installed on the end user system, and if the user 
experience is the same
the average user won't even know something has changed.

cheers,

G.

Re: new version python3

[Daniel Echeverry]

Hi!

2015-12-21 17:18 GMT-05:00 Gianfranco Costamagna
:
> Hi,
>
>>I am working in a new version of lfm, the new version is python3 for
>>this reason I want to know if necessary create a ITP bug with a new
>>package like this lfm3, to package this new version, or if I could
>>continue with the same package.
>
>
> the question is:
>
> is this something that the average normal use will notice or care about?
> e.g. if the user experience won't change, and the upstream development has 
> moved to python3 only
> seems legit to just switch the dependencies.
>
> Moreover nowadays both are installed on the end user system, and if the user 
> experience is the same
> the average user won't even know something has changed.
>
> cheers,
>
> G.

I am not sure but upstream provides something [1] A lot of changes and
the new version is written from scratch what do you think ?

Also the python2 version is orphan, the upstream doesn't provide support

Really, thank you very much!

Regards

[1]: https://inigo.katxi.org/devel/lfm/#upgrading-from-2-x-to-3-x

-- 
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
Linux user: #477840
Debian user
Software libre

Re: new version python3

[Ben Finney]

Daniel Echeverry  writes:

> I am working in a new version of lfm, the new version is python3 for
> this reason I want to know if necessary create a ITP bug with a new
> package like this lfm3, to package this new version

The name ‘lfm3’ implies you are packaging version 3 *of lfm*. Is that
the case for this package?

To put the version of LFM in the package name also implies LFM 3 and
some other version of LFM (version 2, or version 4, etc.) are likely
candidates to be installed on the same system. Is that true for this
case?

The implementation language of the program is generally quite irrelevant
to what the program should be called.

An exception would be if the program's purpose is primarily *about* that
language, such as a development tool for that language. Is that the
case for this program?

> or if I could continue with the same package.

If the change of implementation doesn't entail a significant change in
how the program is expected to behave, then yes, I think keeping the
package name the same is important to reflect that continuity.

-- 
 \  “Generally speaking, the errors in religion are dangerous; |
  `\those in philosophy only ridiculous.” —David Hume, _A Treatise |
_o__)   of Human Nature_, 1739 |
Ben Finney