I didn't know about the freshport patches until you mentioned that in your
previous comment. I'm not that familiar with FreeBSD. Anyway, I haven't see any
PR with these patches, but some of them are actually already covered by
branches.
--
sorry i somehow missed your answer. can not subscribe to this thread somehow.
can you subscribe me as branch owner?
it is ok to have a vanilla way to install the software. it just needs to be
maintained.
and independent of this: we should bring the freshport patches somehow upstream
and
I use the script to quickly set-up my environment without depending on the
port. I understand that the port is definitely a better solution most of the
time, but it's also good to have a vanilla way to install the software.
--
i wonder if tools/build-on-freebsd could not be dropped completely as there is
an official freshport in the meanwhile:
https://www.freshports.org/net/cloud-init/
the port is version 18.3 and includes just some FreeBSD specific patches out of
which i know some are 100% obsolete in the
I use the following script to prepare my FreeBSD images, my freebsd branch
comes with all the patches from my different branches:
https://github.com/virt-lightning/freebsd-cloud-images
Python3 is on my TODO list, with a lower priority. If you open a bug, you can
affect it to me.
--
This looks like a reasonable set of changes to me; is there any good way for me
to test it? (Perhaps in a container/public cloud?)
Also, do we need to open a bug for converting this script to Python 3 in
preparation for dropping Python 2 support from cloud-init[0]?
[0]
Gonéri Le Bouder has proposed merging ~goneri/cloud-init:build-on-freebsd into
cloud-init:master.
Commit message:
freebsd: add chpasswd pkg in the image
cc_set_passwords.py depends on chpasswd binary.
Requested reviews:
cloud-init commiters (cloud-init-dev)
For more details, see:
7 matches
Mail list logo
