~dcrck

~dcrck/meerific

Last active a month ago
View more

Recent activity

[PATCH builds.sr.ht v6] add Void Linux build image a month ago

From Derek to ~sircmpwn/sr.ht-dev

This commit adds the scripts necessary to build and run Void Linux.
They're based on the official instructions [1] and the Fedora image,
which takes a similar approach.

Void Linux is a rolling release distro, but it allows users to pick
between two C standard libraries: glibc and musl. Thus, it includes two
"libc" release directories: `void/musl` and `void/glibc`. Specifying
the `void` parent directory selects `glibc` by default.

I checked several times for typos, but please let me know if I missed
any!

[1]: https://docs.voidlinux.org/installation/guides/chroot.html
---
[message trimmed]

Re: [PATCH builds.sr.ht v5] add Void Linux build image a month ago

From Derek to ~sircmpwn/sr.ht-dev

On Feb 22, 2021, at 5:55 AM, Drew DeVault <sir@cmpwn.com> wrote:
> Sorry for the delay in reviewing this, not a high priority right now.

I don’t mind; I’m asking a lot, take all the time you need.

> glibc is a libc, not a compiler
Yep, that makes sense, I’ll change that variable name.

> What is the size of the base install?

From the docs[1], it looks like it’s 600-700MB. Should I give it 1-2GB just to be
safe?

> We recently changed how we do DNS in build images: add two nameservers,

[PATCH builds.sr.ht v5] add Void Linux build image 2 months ago

From Derek to ~sircmpwn/sr.ht-dev

This commit adds the scripts necessary to build and run Void Linux.
They're based on the official instructions [1] and the Fedora image,
which takes a similar approach.

Void Linux is a rolling release distro, but it allows users to pick
between two C compilers: glibc and musl. Thus, it includes two
"compiler" release directories: `void/musl` and `void/glibc`. Specifying
the `void` parent directory selects `glibc` by default.

I checked several times for typos, but please let me know if I missed
any!

[1]: https://docs.voidlinux.org/installation/guides/chroot.html
---
[message trimmed]

[PATCH builds.sr.ht v4] add Void Linux build image 2 months ago

From Derek to ~sircmpwn/sr.ht-dev

This commit adds the scripts necessary to build and run Void Linux.
They're based on the official instructions [1] and the Fedora image,
which takes a similar approach.

Void Linux is a rolling release distro, but it allows users to pick
between two C compilers: glibc and musl. Thus, it includes two
"compiler" release directories: `void/musl` and `void/glibc`. Specifying
the `void` parent directory selects `glibc` by default.

I checked several times for typos, but please let me know if I missed
any!

[1]: https://docs.voidlinux.org/installation/guides/chroot.html
---
[message trimmed]

Re: [PATCH builds.sr.ht v3] add Void Linux build image 2 months ago

From Derek to ~sircmpwn/sr.ht-dev

On Jan 18, 2021, at 8:43 PM, Drew DeVault <sir@cmpwn.com> wrote:
> 
> We could just make it a separate release, e.g. void/musl and void/glibc.

Gotcha, similar to how versions work in other distros. I thought of that right after I sent the email. Okay, makes sense, I can do that.

Re: [PATCH builds.sr.ht v3] add Void Linux build image 2 months ago

From Derek to ~sircmpwn/sr.ht-dev

On Jan 18, 2021, at 2:39 PM, Drew DeVault <sir@cmpwn.com> wrote:
> I think that we ought to support both. Please update this patch to
> include that variable.

Okay, that’s fair enough. I’ll do that. Looking at the build manifest 
reference, it isn’t obvious where I’d specify the compiler variant. 
Here are some options I’m considering:

- encoding it in the `arch` property, e.g. “x86_64-musl"
- adding it to the optional `repositories` property, although 
   that seems to be for extra repositories rather than required ones
- adding a `compiler` variable to the `environment` property, 
  where users would put either `glibc` (default) or `musl`

Re: [PATCH builds.sr.ht v3] add Void Linux build image 2 months ago

From Derek to ~sircmpwn/sr.ht-dev

On Jan 18, 2021, at 12:16 PM, Drew DeVault <sir@cmpwn.com> wrote:
> What flavor of Void does this use? glibc or musl?

The genimg script uses the glibc repository.

From the docs[1]:

> The locations of the main repository in relation to a base mirror URL are:
> - glibc: /current
> - musl: /current/musl
> - aarch64 and aarch64-musl: /current/aarch64

Line 43 of the genimg script:

[PATCH builds.sr.ht v3] add Void Linux build image 2 months ago

From Derek to ~sircmpwn/sr.ht-dev

This commit adds the scripts necessary to build and run Void Linux.
They're based on the official instructions [1] and the Fedora image,
which takes a similar approach.

Void Linux is a rolling release distro, so I don't think I need any of
the versioning directories that other images have.

I checked a few times for typos, but please let me know if I missed any!

[1]: https://docs.voidlinux.org/installation/guides/chroot.html
---
This patch update explicitly disables the DHCP client since we're using
a static network configuration
[message trimmed]

[PATCH builds.sr.ht v2] add Void Linux build image 2 months ago

From Derek to ~sircmpwn/sr.ht-dev

This commit adds the scripts necessary to build and run Void Linux.
They're based on the official instructions [1] and the Fedora image,
which takes a similar approach.

Void Linux is a rolling release distro, so I don't think I need any of
the versioning directories that other images have.

I checked a few times for typos, but please let me know if I missed any!

[1]: https://docs.voidlinux.org/installation/guides/chroot.html
---

Fix issues from last patch:
[message trimmed]

Re: [PATCH builds.sr.ht] add Void Linux build image 2 months ago

From Derek to ~sircmpwn/sr.ht-dev


> On Jan 10, 2021, at 11:32 AM, Drew DeVault <sir@cmpwn.com> wrote:
> We'll also need the following:
> 
> - Instructions I can follow to bootstrap the build image from a Void VM

This means showing what Void-specific stuff goes in the build.yml file, right? Okay, I can do that:

Install the following packages:
- dbus
- libvirt
- qemu