From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu From: "peter a. cejchan" Message-ID: <71652467.0206120322.71ca293@posting.google.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit References: Subject: Re: [9fans] One more silly question Date: Wed, 12 Jun 2002 12:36:33 +0000 Topicbox-Message-UUID: aa5d1646-eaca-11e9-9e20-41e7f4b1d025 rob@plan9.bell-labs.com (rob pike, esq.) wrote in message news:... > > why doesn't 'install' target in /sys/src/cmd/mklib cp also $HFILES? > > Because HFILES might include private implementation files that > should not be copied. > > > Is this a clean solution to it? > > > > installh:V: install > > cp $HFILES $home/include/ > > > > Sure, if that's what you want, but since when is $home an installation > directory for system libraries? This looks like a fine rule for the mkfile > of a private program but is not suitable for /sys/src/cmd/mklib. > > -rob I did not mean to change/sys/src/cmd/mklib -- just needed a solution for a private program(s) that need to be linked against a (non-system) lib. perhaps it is unwise, but I keep all my stuff under $HOME hierarchy, binding what I need to proper (?) system dirs. ++pac