[haiku-commits] Re: r36001 - in haiku/trunk: data/system/data/licenses src/apps/aboutsystem
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Tue, 30 Mar 2010 15:39:26 +0200
On 2010-03-30 at 07:22:14 [+0200], Matt Madia <mattmadia@xxxxxxxxx> wrote:
> Here's a preliminary patch to help meet the license requirements:
> Index: /haiku-src/haiku-svn/src/libs/pdflib/Jamfile
> ===================================================================
> --- /haiku-src/haiku-svn/src/libs/pdflib/Jamfile (revision 35990)
> +++ /haiku-src/haiku-svn/src/libs/pdflib/Jamfile (working copy)
> @@ -1,3 +1,9 @@
> SubDir HAIKU_TOP src libs pdflib ;
>
> SubInclude HAIKU_TOP src libs pdflib libs ;
> +
> +# Copy documentation as per license requirement.
> +CopyDirectoryToHaikuImage system documentation
> + : [ FDirName $(HAIKU_TOP) src libs pdflib doc ]
> + : pdflib : -x .svn ;
> +
The *ToHaikuImage rules should not be invoked, directly or indirectly, from a
Jamfile (with the possible exception of the root Jamfile). So either move
this to HaikuImage or introduce a rule to associate additional
files/directories with targets. There are already similar solutions for the
wifi firmware and, since yesterday, for the application catalogs. Maybe it's
time to introduce a generic solution.
> =-=-=
> Something like this is needed to copy the sample programs,
> but i'm not sure about the destination directory
>
> CopyDirectoryToHaikuImage develop sample-code
> : [ FDirName $(HAIKU_TOP) src libs pdflib bind ]
> : pdflib : -x .svn ;
BeOS had the sample-code directory in /boot/optional, but I think
/boot/develop is indeed a better choice.
CU, Ingo
Other related posts:
