From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <20100325114948.GA7249@polynum.com> <20100326013648.GA9563@zoidberg.hsd1.mi.comcast.net> Date: Fri, 26 Mar 2010 02:52:09 -0300 Message-ID: <32d987d51003252252l3528c3ebqcb8987bcdc7dd619@mail.gmail.com> From: "Federico G. Benavento" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] Man pages for add-ons Topicbox-Message-UUID: f348064e-ead5-11e9-9d60-3106f5b1d025 ok, what about libraries, are you going to add a new place for included files or have a script that sets the namespace for every library a program you want to compile needs? think about python for instances, it's needs zlib, bzip2, openssl and it couldn't depend even on more stuff (like libxml, sqlite, curses, etc), but I tried to keep it simple, but usable and then you also have the configuration files, binds are find, but you need a big amount of them to get something going.... in the end you have to think in the actual usage. I chose to "pollute" /sys/src/cmd with non standard packages for all of the above reasons and some that don't come to my mind right now. but there was the precedent of the .iso.bz2 packages like perl, TeX, python, even the old X11 port. contrib allows -r to choose the root so you can live without "polluting" /, but then you have to work your bind magic, do it and tell me how it goes when you want to run configure to port something -- Federico G. Benavento