Subject: Re: CVS commit: pkgsrc/devel/py-Pyro
To: None <darcy@NetBSD.org>
From: Min Sik Kim <minskim@NetBSD.org>
List: pkgsrc-changes
Date: 01/02/2005 06:56:58
On Sun, 2 Jan 2005 06:31:43 -0500
"D'Arcy J.M. Cain" <darcy@NetBSD.org> wrote:
> On Sat, 1 Jan 2005 20:35:15 -0600
> Min Sik Kim <minskim@NetBSD.org> wrote:
> > Please read the TODO file before you import a package from pkgsrc-wip.
>
> I did.
>
> > As TODO says, this package currently conflicts with many other
> > packages, including itself with different PYPKGPREFIX.
>
> Are you talking about the TODO in the package itself? That file says;
>
> "Make scripts installed with ${PYPKGSUFX} so they don't conflict each
> other
> when it is installed for >1 versions of Python."
>
> Now, it may be that the scripts conflict with other programs but I read
> this as being a nice-to-have for situations where someone has more than
> one version of Python installed and wants Pyro for all of them. It is
> still a useful package in the usual case.
A user may install it with different versions of Python without
knowing that they will conflict. After deinstalling one of them,
he/she will find that the package doesn't work any more due to missing
files.
Such a scenario should not happen in pkgsrc. If the problem is
already known, it should be fixed in pkgsrc-wip. IMO, it is not just
a nice-to-have but a must.
> Do you know of any conflicts with other packages? That would be a
> different issue and would probably warrant a CONFLICTS line.
Yes, this is another issue. The following files exist in other
packages' PLISTs.
bin/es in shells/es
bin/ns in net/ns
bin/esd in audio/esound
--
Min Sik Kim