On Wed, Jul 12, 2017 at 10:10:20AM +0100, G.W. Haywood wrote:

[cut]

> My guess is that nobody has yet followed these instructions for a new
> project - at least nobody who was not already sufficiently familiar
> with the process not to need them - because there seem to be places in
> setting up a real project, as opposed to the null demonstration, where
> things need to be done and decisions need to be made which are not
> mentioned in the document. I'm happy to be testing the document. :)

Hi,

thanks for testing the document :)

>
> Adding a public key to the personal profile at git.devuan.org has not
> been mentioned thus far; it is mentioned now to list things to add to
> the document. The need to avoid being sidetracked from the document
> by clicking on any of the many dead links on the git.devuan.org pages
> should also be mentioned. Hopefully when we've reached some sort of
> an artistic conclusion we'll have in this thread a list of the things
> I've learned that weren't documented. :)
>

yes, there are several things to be added. Hope you are keeping a list.

[cut]

> laptop3:/opt/ged/git/devuan/pkg_openvpn/openvpn$ >>> apt-cache policy openvpn
> openvpn:
>   Installed: (none)
>   Candidate: 2.3.4-5+deb8u2
>   Version table:
>      2.4.0-6+deb9u1~bpo8+1 0
>         100 http://auto.mirror.devuan.org/merged/ jessie-backports/main amd64 Packages
>      2.3.4-5+deb8u2 0
>         500 http://auto.mirror.devuan.org/merged/ jessie-security/main amd64 Packages
>      2.3.4-5+deb8u1 0
>         500 http://auto.mirror.devuan.org/merged/ jessie/main amd64 Packages

>
> Assuming I want to put OpenVPN in Devuan jessie, how do I choose from
> the offered packages (i.e. "what are the decision making processes?",
> not "what is the answer?"). I'm guessing that my next step will be


The next step depends on which release you would like to build your
package for. Now, the norm would be to build for unstable, and have
the packages "percolate" down to testing and then
backports/updates. However, in Devuan this flow has been interrupted,
since we started working on Jessi which was already frozen.

In other words: If you want to have your de-systemd-ised package in
jessie, at this point you should build for
jessie-proposed-updates. This means that you should get the latest
available version in Jessie (in this case it might be 2.3.4-5+deb8u2)
and prepare a "jessie-proposed-updates" branch.

Hope this helps. Please shout if you need help, or come to
#devuan-dev, which is quicker.

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[     "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[       @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[     @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]