Date: Sat, 16 Aug 2014 11:41:48 +0200 From: Matthias Andree <matthias.andree@gmx.de> To: freebsd-ports@freebsd.org Subject: Re: Ports, pkg's confusion on upgrades... Message-ID: <53EF275C.9040700@gmx.de> In-Reply-To: <2A69DCE1B30998B865D46192@Mail-PC.tdx.co.uk> References: <52652ABEC925BB93CB8877CD@Mail-PC.tdx.co.uk> <53EDE679.9050105@wasikowski.net> <2A69DCE1B30998B865D46192@Mail-PC.tdx.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 15.08.2014 um 14:43 schrieb Karl Pielorz: >=20 >=20 > --On 15 August 2014 12:52 +0200 =C5=81ukasz W=C4=85sikowski > <lukasz@wasikowski.net> wrote: >=20 >> You could solve this by using your own poudriere - create repos with >> your own port's options and pkg upgrade everything. Your current >> approach - mixing packages and ports - is not supported IIRC. >=20 > Thanks for the suggestion - and I take your point about not mixing port= s > & packages... >=20 > Setting up our own pkg repo though sounds like a lot of work (all for > the sake of about probably 2 packages we need to change the options on) > - I'd guess there's no way of telling pkg to use 'our' repo for these > 2-3 packages, and the main one for everything else? >=20 > I suppose the other option is just ignore packages, and stick to ports? > (presuming ports will always be around :) Building ports is sometimes more effort than doing a clean-room build with, say, poudriere. I recently upgraded OpenEXR from 2.1 and 2.2 (as port maintainer) and had to patch the upstream source so 2.2 would build with 2.1 pre-installed. These issues never show under poudriere, which is why some people are considering ports "obsolete". I am not one of these people. > I'd also still like to know if there's a way of getting 'pkg upgrade' t= o > spit out why it wants to install a 'new package' - when none of the > current packages have a dependency on it? Likely either because the new version that would get installed requires those, or because current pkg versions are rather buggy with respect to shared library dependencies. AFAICS this is going to be fixed only after a pkg 1.3.7 release and the subsequent full pkg rebuild. The other issue I found is that you cannot install a locked package from ports either because pkg will refuse to deinstall the old version. There would need to be a limited lock, perhaps a "hold" or "no-remote" or "no-upgrades" that only affects "pkg upgrade" and downloads but not local deinstalls/install. I'm not too hopeful though...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53EF275C.9040700>