[haiku-bugs] Re: [Haiku] #10190: Make Bluetooth stack an actual HPKG via build system

  • From: "bonefish" <trac@xxxxxxxxxxxx>
  • Date: Sun, 10 Nov 2013 23:57:30 -0000

#10190: Make Bluetooth stack an actual HPKG via build system
   Reporter:  mmadia        |      Owner:  bonefish
       Type:  task          |     Status:  new
   Priority:  normal        |  Milestone:  R1
  Component:  Build System  |    Version:  R1/Development
 Resolution:                |   Keywords:
 Blocked By:                |   Blocking:
Has a Patch:  1             |   Platform:  All

Comment (by bonefish):

 While building separate packages for bluetooth, userlandfs, canna, etc. is
 the thing to do, I don't think they should be put on the image, unless
 they are also activated. The intended solution is to have BuildBot (or
 whatever tool we're going to use) build not only the Haiku image, but also
 a package repository with all packages produced by the build system,
 including the optional ones. The user will then be able to install them
 like any other package, and updates will work as well, when the repository
 is updated.

 Building said package repository is on Oliver's TODO list, but in case he
 doesn't finish it before his vacation, maybe you want to set this up on
 your server temporarily. The only thing missing in the build system beside
 the definition of all the optional packages (mostly for convenience) would
 be a target or build profile action to create a directory with all the
 properly named packages.

 Regarding your patch:
 * As written above, the package should not be added to the image. There's
 no need for the optional package section anymore.
 * The package definition looks OK. I suppose the Deskbar entry should go
 under Preferences, though.
 * The development stuff should probably go in a separate devel package.
 Since it is not that much, the package can be defined in the same file.
 The bluetooth headers should be added there as well and excluded from the
 haiku_devel package.
 * Since there's a library, we'll need a set of packages for the secondary
 architecture as well.
 * Regarding the package info:
   - The architecture should not be "any". Cf. e.g. the haiku_devel package
 info for how it should be specified.
   - A more ... uh ... descriptive description would be nice.
   - The "provides" section should include an entry for the library
 ("lib:libbluetooth = %HAIKU_VERSION%" compat >= ..." (don't know how far,
 if at all, it is backward compatible)).
   - The "provides" section should include "cmd:..." entries for the
 command line tools (same versions).
   - The "requires" section should at least include an entry for "haiku".
 Cf. the package info for haiku_devel, though it probably doesn't need to
 be marked "base". Don't know, if there are any other requirements.

Ticket URL: <http://dev.haiku-os.org/ticket/10190#comment:3>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: