Date: Mon, 12 Apr 2010 09:18:19 -0700 From: Garrett Cooper <yanefbsd@gmail.com> To: Leinier Cruz Salfran <salfrancl.listas@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: make pkg_install suite reusable, please Message-ID: <l2r7d6fde3d1004120918y9f6d08d7y2628831c2bcf33a9@mail.gmail.com> In-Reply-To: <k2qa2585ef1004120907w8e87f21cua0ef7ff1d0410e63@mail.gmail.com> References: <x2ta2585ef1004090716vf74893dfo9d5412455294c64d@mail.gmail.com> <q2x3cb459ed1004090736t5a67f315geca1c199a5061e7d@mail.gmail.com> <alpine.BSF.2.00.1004111235330.80625@fledge.watson.org> <hptpq8$klh$1@dough.gmane.org> <k2qa2585ef1004120907w8e87f21cua0ef7ff1d0410e63@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 12, 2010 at 9:07 AM, Leinier Cruz Salfran <salfrancl.listas@gmail.com> wrote: > On Sun, Apr 11, 2010 at 8:34 PM, Marcin Wisnicki > <mwisnicki+freebsd@gmail.com> wrote: >> On Sun, 11 Apr 2010 12:37:27 +0100, Robert Watson wrote: >> >>> On Fri, 9 Apr 2010, Alexander Churanov wrote: >>> >>>> 2010/4/9 Leinier Cruz Salfran <salfrancl.listas@gmail.com> >>>> >>>>> i want to ask you one thing: can you make the 'pkg_install' suite >>>>> reusable .. means install 'libinstall.a' as a shared object in order >>>>> to make it reusable by others devs >>>> >>>> I'd like to add my 50 cents. From my point of view, the true UNIX way >>>> is re-using whole programs. This provides unbelievable isolation and >>>> correctness. If you don't want to fork myriads of processes each >>>> second, then, it's, probably, better to ask for pipe mode of pkg_* >>>> tools. For example, aspell works that way. You start a process, write >>>> commands and queries and read results. >>> >>> While there are clearly benefits to process isolation, there are >>> countless situations in UNIX where I've said to myself "Oh, I wish I ha= d >>> a lib<foo> not just a <foo> command". =A0This is particularly the case = for >>> monitoring tools, where third-party applications have a lot of trouble >>> parsing and tracking the output of tools like ps(1), etc. =A0This is wh= y >>> recently we've been working on libmemstat(3), libprocstat(3), >>> libnetstat(3), etc -- so that tools can avoid rewriting that code as >>> well as avoid the parsing problem. >> >> A middle-ground solution to this is to standardise on a common data >> exchange format with a schema definition language. With schema you can >> autogenerate high level parsers and generators, validators and other thi= ngs >> for free. It does not have to be XML with XML-Schema (though there are g= ood >> plaintext schema languages like RelaxNG-compact and you could possibly f= ind >> less verbose text encoding for XML). >> >> If, say ps or ipfw, had a switch like '--format-output-yaml' and >> '--print-output-schema' (alternatively schema files could be stored >> somewhere in $prefix/share) it would be trivial to use them anywhere. >> >> The only problem I see is agreeing on a single format and forcing everyo= ne >> to use it. Which is probably why it will never happen :( >> > > hello marcin > > that can be a smart solution but i prefer to use functions directly > from library .. i think it's better > > well, alexander .. i must to follow your first suggestion: use 'pkg_*' > commands (meanwhile) .. i plan to make this software usable to netbsd > and openbsd too .. =A0i'm not sure but maybe they have the same > situation and for that reason i think use the commands is the way to > follow Just to give you an idea of what's out there... NetBSD used the same basic solution that FreeBSD did, but they diverged about 3 years ago and they have their own library based solution. I think that OpenBSD has their own package maintenance tool written in perl. As for us, we're going the libpkg direction-ish AFAIK, but it's going to take time before we get there. In the meantime, there's also a tool named pkgin which does similar to what you describe and it's portable between pkg_install on FreeBSD and the libpkg-ish solution on NetBSD. HTH, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?l2r7d6fde3d1004120918y9f6d08d7y2628831c2bcf33a9>