DatumHueEnterprise v0.0.24datumhue.com
Contents

12345678Build a ball pit · Step 8 of 8

Share it

You'll learn10 min
  • Choose a title and a license
  • Check a package with pkg check
  • Pack it with pkg pack
Time
10 min
Builds on
Step 7: Test it

Your ball pit is ready for other people. In this step you give it a title and a license, check it, and pack it into one file that anyone with DatumHue can run.

Give it a title and a license

People see a package by its title. Without one, DatumHue makes a title from the name: @alice/ball-pit reads Ball Pit. A title can say more than a name can, with capitals, spaces and punctuation.

The license says what others may do with your package. List the licenses DatumHue accepts with pkg license:

sh
$ datumhue pkg license

pkg new chose 0BSD: anyone may use the package for anything. To let anyone play your pit while you keep every other right, pick LicenseRef-DatumHue-Freeware. Package licenses holds the full text of each.

Open ballpit/package.kdl, add a title and a description, and change the license:

ballpit/package.kdlkdl+3 new, 1 removed
name "@alice/ball-pit"
New line: title "Alice's Ball Pit"
New line: description "Balls that fall, bounce and pile up."
version "0.1.0"
api_version "*"
kind "app"
New line: license "LicenseRef-DatumHue-Freeware"
  • title is one line of at most 40 characters.
  • description says in a sentence what the package is.

Check and pack it

Check the package, then pack it:

sh
$ datumhue pkg check ballpit
$ datumhue pkg pack ballpit
  • pkg check reads the manifest and the package's files. It prints a line that starts with OK, or each problem it finds.
  • pkg pack writes the package into one file, an archive, next to the folder. Its name comes from the package's name and version: alice-ball-pit-0.1.0.dhpkg. It holds the manifest, init.lua and lib/; the tests, the README and the editor files stay behind.

Run the archive as the people you send it to will:

sh
$ datumhue run alice-ball-pit-0.1.0.dhpkg

The pit starts with the balls you left in it. Run from its folder or from its archive, it is the same package, with the same store.

Publish it

Publishing puts your package in the registry that serves its namespace, where everyone who uses the deployment can install it. Sign in with datumhue login, then push the package's folder with pkg push:

sh
$ datumhue login
$ datumhue pkg push ballpit

Your sign-in must own the package's scope, so before you push, change @alice in the manifest's name to your own scope. Publish and maintain a release covers dependencies, new versions and retiring a release.

Try this

  • Raise version to 0.2.0 and pack again. What is the new archive called?
  • List what the archive holds with datumhue pkg ls alice-ball-pit-0.1.0.dhpkg.
  • Unpack the archive into a new folder with datumhue pkg unpack, and run that folder.

Recap

  • title is the name people see. license says what they may do with your package.
  • datumhue pkg check checks a package without packing it.
  • datumhue pkg pack makes a .dhpkg archive, which datumhue run runs as it runs a folder.

datumhue.com

(c) 2026 Shuusei AB. Quote excerpts of this manual, with attribution to DatumHue, in your own documentation, tutorials, course materials, reviews, and other writing or video. Republishing it in whole or in substantial part needs written permission: support@datumhue.com.

Victor Mono is licensed under the SIL Open Font License 1.1
Copyright (c) 2024, Rune Bjørnerås (https://github.com/rubjo)

This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is copied below, and is also available with a FAQ at:
http://scripts.sil.org/OFL


-----------------------------------------------------------
SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
-----------------------------------------------------------

PREAMBLE
The goals of the Open Font License (OFL) are to stimulate worldwide
development of collaborative font projects, to support the font creation
efforts of academic and linguistic communities, and to provide a free and
open framework in which fonts may be shared and improved in partnership
with others.

The OFL allows the licensed fonts to be used, studied, modified and
redistributed freely as long as they are not sold by themselves. The
fonts, including any derivative works, can be bundled, embedded,
redistributed and/or sold with any software provided that any reserved
names are not used by derivative works. The fonts and derivatives,
however, cannot be released under any other type of license. The
requirement for fonts to remain under this license does not apply
to any document created using the fonts or their derivatives.

DEFINITIONS
"Font Software" refers to the set of files released by the Copyright
Holder(s) under this license and clearly marked as such. This may
include source files, build scripts and documentation.

"Reserved Font Name" refers to any names specified as such after the
copyright statement(s).

"Original Version" refers to the collection of Font Software components as
distributed by the Copyright Holder(s).

"Modified Version" refers to any derivative made by adding to, deleting,
or substituting -- in part or in whole -- any of the components of the
Original Version, by changing formats or by porting the Font Software to a
new environment.

"Author" refers to any designer, engineer, programmer, technical
writer or other person who contributed to the Font Software.

PERMISSION & CONDITIONS
Permission is hereby granted, free of charge, to any person obtaining
a copy of the Font Software, to use, study, copy, merge, embed, modify,
redistribute, and sell modified and unmodified copies of the Font
Software, subject to the following conditions:

1) Neither the Font Software nor any of its individual components,
in Original or Modified Versions, may be sold by itself.

2) Original or Modified Versions of the Font Software may be bundled,
redistributed and/or sold with any software, provided that each copy
contains the above copyright notice and this license. These can be
included either as stand-alone text files, human-readable headers or
in the appropriate machine-readable metadata fields within text or
binary files as long as those fields can be easily viewed by the user.

3) No Modified Version of the Font Software may use the Reserved Font
Name(s) unless explicit written permission is granted by the corresponding
Copyright Holder. This restriction only applies to the primary font name as
presented to the users.

4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
Software shall not be used to promote, endorse or advertise any
Modified Version, except to acknowledge the contribution(s) of the
Copyright Holder(s) and the Author(s) or with their explicit written
permission.

5) The Font Software, modified or unmodified, in part or in whole,
must be distributed entirely under this license, and must not be
distributed under any other license. The requirement for fonts to
remain under this license does not apply to any document created
using the Font Software.

TERMINATION
This license becomes null and void if any of the above conditions are
not met.

DISCLAIMER
THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
OTHER DEALINGS IN THE FONT SOFTWARE.

Try

    ↑↓ selectEnter openTab filter

    Settings

    Theme
    Text
    Print

    Keyboard shortcuts

    / or Ctrl KSearch
    ↑ ↓ EnterPick a result
    TabNext result filter
    j kNext or previous entry
    [ ]Previous or next page
    yCopy a link to the current entry
    ?These shortcuts
    EscClose

    On this page