[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: How to deal with packages having the same files
Well, there is a difference - py27-qt5 and py37-qt5 are the same
package built with different PYTHON_VERSION_DEFAULT; you wouldn't have
them both at the same time generally; if you switch the python
version, you are supposed to rebuild all dependent packages anyway -
although I've had occasions where I, whilst using 3.7 as the default
python, I had to change to 2.7 to upgrade some specific package. In my
case, gcr and gnome-keyring are related and used by different packages
down the line, which could in principle be installed at the same time.
It is one of thise things complex packaging systems like pkgsrc have
to deal with and there is not always a pretty solution.
On Tue, 14 Jan 2020 at 22:18, Rhialto <rhialto%falu.nl@localhost> wrote:
> On Tue 14 Jan 2020 at 23:00:32 +0100, Rhialto wrote:
> > Would it make sense to rename these files to py7-pylupdate5,
> > or pylupdate5-py7, or pylupdate7-5, or ... ? Or do something
> > with ALTERNATIVES, such as with devel/py-test-watch/ALTERNATIVES?
> There are also bin/pyrcc5 and bin/pyuic5, and I assume they are
> sometimes used when building depending packages, which would break with
> a renaming (so that would need extra fixing).
> Olaf 'Rhialto' Seibert -- rhialto at falu dot nl
> ___ Anyone who is capable of getting themselves made President should on
> \X/ no account be allowed to do the job. --Douglas Adams, "THGTTG"
Main Index |
Thread Index |