Message-ID: <1794908211.2291.1369290983724.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2290_979743680.1369290983723" ------=_Part_2290_979743680.1369290983723 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page will attempt to summarize the generalities in= volving creating binary packages (.rpm, .deb, what have you) of boo. The sp= ecifics of each packaging system are beyond the scope of this document. Ple= ase refer to the documention for whatever packaging system you are using fo= r any of those specifics.
Having acknowledged that packaging nant is currently both a daunting, an= d seemingly pointless endevour for most packagers, boo releases starting wi= th boo-0.5.3 have included a autotools generated tarball which includes all= of the necessary pieces to do a binary install of boo. Th= e only way to compile boo currently is to use NAnt. Duplicating the entire = build system in both nant and autotools is not currently a goal or priority= for anyone actively contributing to boo. Those wishing to package boo as b= uilt from source should take a look at the how to compile = boo page for more details.
Currently, the autotooled tarballs depend on having shared-mime-info= .pc and gtksourceview-1.0.pc around during the configure stag= e. This is to ensure that the proper location for the mime and gtksourcevie= w stuff for the system is detected.
gacutil is also required to install the boo libraries into the = GAC.
The installation process for the tarballs is just like any other autotoo= ls using project:
$ ./configure --prefix=3D/some/prefix
$ make (doesn't really do anything, as everything is compiled already)
$ make DESTDIR=3D/some/fake/root install
Packagers should note that as usual the DESTDIR variable can/should be o= verriden to point to any "fake root" that may be used to create p= ackages.
Any issues with or questions regarding the tarballs can be directed to t= he Boo development list, latexer on IRC in #boo on irc.codehaus.or= g, or to Pete directly by emailing latexer AT please_remove_me_when_emailin= g gentoo DOT org.
Currently the binary packages do not install the boo nant task assembly = into any place where nant can find it. Packagers wishing to make the boo na= nt tasks available in any nant packages they may have will want to take car= e to put the Boo.NAnt.Tasks.dll inside whatever directory the rest of the n= ant assemblies live in.------=_Part_2290_979743680.1369290983723--