Forum #6 - Topic #20 - Message List

Naming/Packaging

As CWiid becomes more popular and is included in various distributions, package granularity is becoming an issue. Basically, I'm thinking about separate libwiimote (including wmdemo), and cwiid utils packages (wminput could arguably be its own package). If we do that, though, I think libwiimote should be renamed libcwiid, and the function, type, and constant prefixes changed to cwiid. This would be moderately disruptive, but it would reduce confusion with other packages (libwiimote). Thoughts?

dsmith
04/07/07 09:23:43
Tree View Flat View (newer first) Flat View (older first)
  • Message #82

    This sounds like the right path to take to me. Three different packages make sense: cwiid (wminput), cwiid-dev (libwiimote), and cwiid-utils (all other cwiid related applications).

    Changing the name of libwiimote is probably a good idea at this point in time. It would definitely be easier than doing it when cwiid becomes more widely used.

    nickishappy
    04/07/07 20:21:29
    • Message #88

      I was thinking libcwiid, cwiid-wminput, and cwiid-utils. In Debian package naming parlance, I believe cwiid-dev implies headers for cwiid, which isn't really the case. Not sure about that though, I run Gentoo where everything is a dev package.

      I've worked on the roadmap a bit and added a 0.6.00 milestone with some tickets against it, including the rename.

      dsmith
      04/09/07 18:40:00
Tree View Flat View (newer first) Flat View (older first)