[Blend-tinker-devel] HyperBorg introduction

[Jonas Smedegaard]

Quoting Imre Nagy (2021-08-25 20:29:42)
> Hi All and hi Jonas,

Hi Imre,

First a meta remark: Best if you subscribe to the list with the address 
you use to post to the list.  If you post from other addresses not known 
to the list, then it will be delayed until it can be manually screeened 
for spam.  Not a problem for me, but takes more time for your post to 
enter the list. :-)


> HyperBorg POC is working in my house, the GUI needs some more days to 
> get POC level, but it is now considered stable. Not too much features, 
> but stable.

Exciting!  Congratulations with this milestone for your project!

Perhaps that is a good time to tag the source as a preliminary v0.0.1 
release?


> Since bullseye is out, it would not interfere with the release cycle. 
> So, closing to POC, I would kindly ask you what informations you need 
> to be able to put HyperBorg into Debian?

No need to worry about our packaging work interfering with release of 
the Debian distro: During the "freeze" of the distro, uploads to the 
"unstable" repo is blocked but then we can upload to the "experimental" 
repo until the "unstable" repo is unblocked again.  Also, we will want 
to upload to the experimental repo anyway, until the package is in a 
generally usable state.


> What it has:
> hynode - this is the main binary
> config.imi - this is the module configufation file  (it's name could be 
> changed)
> hynode.imi - this is the network connection file (it's name could be 
> changed)
> *.so files, these are uploadable plugins
> 
> It is using Qt5 framework, some DB (postgresql, mysql) and this is it 
> mostly.
> 
> I have no knowledge about how a package is created, so might ask thing 
> that are common for you.
> 
> So, is there any checklist of what I should provide for you to make it 
> happen?

Best if you make your project generally buildable - not only for Debian 
but follow standard practices for the kind of coding environment that 
you use.  E.g. document the essential steps of how to build and install 
and configure the software - either in the existing README file or in a 
separate INSTALL file.

When I do the common routines for qmake-based projects, nothing gets 
installed.  So either you need to document the unusual steps I need to 
tak, or (better!) you should try compare your projects to other 
similarly coded projects and register your build objects so that a 
standard build will install your code to standard places.

See https://wiki.debian.org/UpstreamGuide#Releases_and_Versions - and 
the rest of that page as well.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/blend-tinker-devel/attachments/20210825/3bb3c58c/attachment.sig>