Re: CVS commit: pkgsrc/security/py-py-bcrypt

[Richard PALO <richard%netbsd.org@localhost>]

Le 19/04/15 12:52, Greg Troxel a écrit :
> 
> If the issue is really that there are two packages claiming the name
> bcrypt (which was not noted in your commit message), then we need to
> hash out which one gets to own the name and which gets some alternative
> marking.  So I think that's either an -old or an -alternative suffix,
> depending on the preponderance of community view about which way it is.
> Adding a spurious py- just adds to the confusion and doesn't resolve the
> core issue.
> 

Well, this new package is actual the "original" py-bcrypt, as already
stated prior.  

The current py-bcrypt is pkgsrc is actually an alternative
_compatible_ with py-bcrypt (https://github.com/dstufft/bcrypt/)

Is there any real reason not to simply put things in order,
keeping, for lack a better term, the "imposter" as py-bcrypt-alternative?

-- 
Richard PALO