2011/1/21 Xyne <[email protected]>:
> I'm replying because this is tangential... why don't we specify "python3"
> instead of "python" as a dep to make packages future-proof? Even if Python 4
> doesn't come out for a decade or more, it just seems that it would be 
> logically
> consistent.

Hi,

this idea came up last year.
Refer to
     http://mailman.archlinux.org/pipermail/aur-general/2010-July/009504.html

Unfortunately this thread has not been continued.

Since this is a problem for any major release of central dependencies
we should think of a naming policy to avoid transition problems.

Cheers,

Matthias

Reply via email to