[haiku-development] Re: Optional Library Package
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 13 Oct 2010 21:41:04 +0200
On 2010-10-13 at 18:04:52 [+0200], scott mc <scottmc2@xxxxxxxxx> wrote:
> Oh, I should have included this:
> http://ports.haiku-files.org/browser/haikuports/trunk/packs/libpak/libpak-0.9.3.bep
> This is the current .bep file that is used for building the libpak.
> The list of included packages starts on line 19. It calls haikuporter
> for each of the libs and is as maintainable as the current Haiku
> OptionalPackages file. We could separate them all out into individual
> packages and then include them all into a meta package like is done
> with the Development packages. But that would add 50 or so more
> entries to the already growing list of OptionalPackages.
It's not like there's a file size limit. :-) Splitting up the OptionalPackages
file
is absolutely an option, with the individual files moved to a subdirectory.
> The real trick with this package is that they have to be built in a
> certain order so that each of a packages required dependencies are
> built before we build the package itself, so that they get detected
> and used when building the target package.
>
> Speaking of Package Management... right now Haikuporter creates all of
> the resulting packages as .zip files that extract to /boot, putting
> the files in /boot/apps, /boot/common as required. I figure it could
> easily be extended to be the packaging tool that is used for creating
> whatever type of packages we end up creating for the (so far
> unwritten?) Haiku Package Manager. We already have over 300 different
> .bep files written for automated building of packages.
Yep, that's definitely something to leverage once the package management has
emerged
(no reference intended).
CU, Ingo
Other related posts:
