1

Topic: Initiative to create new packages (mBTC for package)

I have some mBTC, and I would like to support creation of new packages in Hyperbola. Currently those which I need. Later I may support more.

Here is software that I need personally:

http://www.pell.portland.or.us/~orc/Code/discount/

https://wiki.gnome.org/Apps/Pinpoint
additionally for Pinpoint, debug it so that videos can play in presentations

emacs-git package, to get latest GNU Emacs from git

clisp-git package, to get latest clisp from git
https://gitlab.com/gnu-clisp/clisp

GNU Mailutils from:
http://gnu.org/s/mailutils
and I propose that mailx package get renamed to mailx and that GNU mailutils get mailutils package name

Postgresql 10 latest version

Courier MTA http://www.courier-mta.org -- and all related packages

2

Re: Initiative to create new packages (mBTC for package)

jmarciano wrote:

http://www.pell.portland.or.us/~orc/Code/discount/

https://wiki.gnome.org/Apps/Pinpoint
additionally for Pinpoint, debug it so that videos can play in presentations

jmarciano wrote:

GNU Mailutils from:
http://gnu.org/s/mailutils
and I propose that mailx package get renamed to mailx and that GNU mailutils get mailutils package name

jmarciano wrote:

Courier MTA http://www.courier-mta.org -- and all related packages

Ok, seems those projects are active and fully free. Open a request about it to HyperTask. You can use FS#117 as example.

jmarciano wrote:

emacs-git package, to get latest GNU Emacs from git

clisp-git package, to get latest clisp from git
https://gitlab.com/gnu-clisp/clisp

We are building all packages from the source through its official tarball not from a version control system (VCS), therefore we won't accept it, except if there aren't available tarballs or GNU/Linux support in those tarballs. (see HTTPS and tarballs amendment in packaging guidelines for further details)

jmarciano wrote:

Postgresql 10 latest version

Unlike Arch and another Arch-based distros, Hyperbola is a LTS one, therefore we won't accept recurrent drastic version changes as long as backporting is possible. (see snapshot versions and backporting amendments in packaging guidelines for further details).

3

Re: Initiative to create new packages (mBTC for package)

I got it, and I could learn how to make PKGBUILD myself.

And where to submit PKGBUILD for future inclusions?

4

Re: Initiative to create new packages (mBTC for package)

jmarciano wrote:

I got it, and I could learn how to make PKGBUILD myself.

There's a manual that comes from pacman with explanation and examples to make PKGBUILDs, run:

$ man PKGBUILD

jmarciano wrote:

And where to submit PKGBUILD for future inclusions?

Open a pull request to HyperTask including your PKGBUILD and files in attachment. Don't forget read our packaging guidelines for further details. smile

5

Re: Initiative to create new packages (mBTC for package)

Emulatorman wrote:
jmarciano wrote:

I got it, and I could learn how to make PKGBUILD myself.

There's a manual that comes from pacman with explanation and examples to make PKGBUILDs, run:

$ man PKGBUILD

jmarciano wrote:

And where to submit PKGBUILD for future inclusions?

Open a pull request to HyperTask including your PKGBUILD and files in attachment. Don't forget read our packaging guidelines for further details. smile

By the way, we're using our mdadm's PKGBUILD as example for all packages. It can be useful as example for your future PKGBUILDs.