Date: Wed, 5 May 2010 00:39:26 -0700 From: Garrett Cooper <yanefbsd@gmail.com> To: Reinhard Haller <Reinhard.Haller@interactive-net.de> Cc: freebsd-current@freebsd.org, Julian Elischer <julian@elischer.org> Subject: Re: ports and PBIs Message-ID: <3F2B5DDD-23EC-4150-91F2-90D0A728DB54@gmail.com> In-Reply-To: <4BE11E4E.5000604@interactive-net.de> References: <4BBFD502.1010507@elischer.org> <4BE11E4E.5000604@interactive-net.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 5, 2010, at 12:29 AM, Reinhard Haller wrote: > Am 04.05.2010 20:40, schrieb Julian Elischer: >>=20 >>>=20 >>> To achieve this goal we get another ports management application and >>> hope it handles also the non trivial tasks of the non simple apps. >>=20 >> there is a PBI helper app. but PBIs are actually executables with the >> installation app built in. >=20 > portupgrade PBIapp should work? I think it's cowsay, not portupgrade, but yes... using multiple tools = would be required AFAIK, because they work at different abstraction = levels. >>>=20 >>> If the PBIs come with all libraries and resources we get even more >>> problems with multiple db installations not less. >>=20 >> not that's the whole point. The app has it's own linraries HIDDEN >> within itself. >> it can not interfere with other apps. >> (except in a port-number manner) but generally >> apps for which PBIs are good do not do that sort of thing. Well, I'm sure there are other conflicts, but that is most likely the = most prevalent issue. Any kind of resource contention where only one of = any given resource that isn't timeshareable is available would be an = issue, or where other potential issues may be like hardcoded paths, = defaults, etc. > Speaking about db installations we end up (worst case) with = imcompatible > files. Thanks, -Garrett=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F2B5DDD-23EC-4150-91F2-90D0A728DB54>