~calebccff

United Kingdon

https://connolly.tech

#Hi, I'm caleb

I write code that solves problems, I mostly work on embedded Linux. I spend a lot of my time working on postmarketOS for the OnePlus 6 and a few other devices. I want to make phones usable beyond the manufacturers lifespan. I also work on whatever else takes my interest...

You can follow me on Twitter

Or on Mastodon Mastodon

~calebccff/pbsplash

Last active 1 year, 11 months ago
View more

Recent activity

Re: [PATCH pmbootstrap] pmb.build: fix local checksums automatically 11 months ago

From Caleb Connolly to ~postmarketos/pmbootstrap-devel


On 14/08/2023 08:36, Oliver Smith wrote:
> On Sun Aug 13, 2023 at 1:41 AM CEST, Caleb Connolly wrote:
>> Add a new "auto_checksum" config option which, when set, will make
>> pmbootstrap fix checksums for local sources in-place before building a
>> package.
>>
>> This _drastically_ speeds up development when working with files that
>> are local to pmaports.
>>
>> It isn't done automatically for remote sources as there is still some
>> value in having these error out (e.g. catching corrupt downloads).
>> Additionally, those sources shouldn't change regularly (if you're doing

Re: [PATCH pmbootstrap] pmb.build: fix local checksums automatically 11 months ago

From Caleb Connolly to ~postmarketos/pmbootstrap-devel


On 14/08/2023 15:55, Oliver Smith wrote:
> On Mon Aug 14, 2023 at 9:36 AM CEST, Oliver Smith wrote:
>> On Sun Aug 13, 2023 at 1:41 AM CEST, Caleb Connolly wrote:
>>> Add a new "auto_checksum" config option which, when set, will make
>>> pmbootstrap fix checksums for local sources in-place before building a
>>> package.
>>>
>>> This _drastically_ speeds up development when working with files that
>>> are local to pmaports.
>>>
>>> It isn't done automatically for remote sources as there is still some
>>> value in having these error out (e.g. catching corrupt downloads).

[PATCH pmbootstrap v4 2/2] pmb.build: add a dirty-build feature for local development 11 months ago

From Caleb Connolly to ~postmarketos/pmbootstrap-devel

With automated checksums, the last piece of the puzzle for quick
development of local packages is to fix the pkgver automatically too.
Add a new --dirty flag to pmbootstrap build which will append the current
datetime to the pkgver. This has two main purposes:
1. Ensures that the newly built package will get picked up by apk
2. Makes it clear that the package is from a local "dirty" build and not
from any binary repo.

The dirty flag only applies when either the local checksums are out of
date, or if the local package source dir has been modified since the
last build. This ensures that only packages the user is working on will
get built when this flag is set.

With this logic in place, it is now sensible to add a '--build' flag to
[message trimmed]

[PATCH pmbootstrap v4 1/2] pmb.build: fix local checksums automatically 11 months ago

From Caleb Connolly to ~postmarketos/pmbootstrap-devel

Add a new "auto_checksum" config option which, when set, will make
pmbootstrap fix checksums for local sources in-place before building a
package.

This _drastically_ speeds up development when working with files that
are local to pmaports.

It isn't done automatically for remote sources as there is still some
value in having these error out (e.g. catching corrupt downloads).
Additionally, those sources shouldn't change regularly (if you're doing
local development like this, please use "pmbootstrap build --src"!)

Enable this option by default, it doesn't introduce any additional risk.
[message trimmed]

[PATCH pmbootstrap v4 0/2] Local development improvements 11 months ago

From Caleb Connolly to ~postmarketos/pmbootstrap-devel

Introdce support for automatically bumping the checksum of local
sources, and for doing "dirty" builds of packages with a custom version
number when there are local changes.

See the individual commit messages for more info.

---
Changes in v4:
- Fix get_pkgver() logic in run_build()
- Fix get_pkgver() arg in envkernel
- Link to v3: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20230813-b4-auto-checksum-v3-0-e5584a5cb7cb@postmarketos.org%3E

Changes in v3:
- Fix build

[PATCH pmbootstrap v3 2/2] pmb.build: add a dirty-build feature for local development 11 months ago

From Caleb Connolly to ~postmarketos/pmbootstrap-devel

With automated checksums, the last piece of the puzzle for quick
development of local packages is to fix the pkgver automatically too.
Add a new --dirty flag to pmbootstrap build which will append the current
datetime to the pkgver. This has two main purposes:
1. Ensures that the newly built package will get picked up by apk
2. Makes it clear that the package is from a local "dirty" build and not
from any binary repo.

The dirty flag only applies when either the local checksums are out of
date, or if the local package source dir has been modified since the
last build. This ensures that only packages the user is working on will
get built when this flag is set.

With this logic in place, it is now sensible to add a '--build' flag to
[message trimmed]

[PATCH pmbootstrap v3 1/2] pmb.build: fix local checksums automatically 11 months ago

From Caleb Connolly to ~postmarketos/pmbootstrap-devel

Add a new "auto_checksum" config option which, when set, will make
pmbootstrap fix checksums for local sources in-place before building a
package.

This _drastically_ speeds up development when working with files that
are local to pmaports.

It isn't done automatically for remote sources as there is still some
value in having these error out (e.g. catching corrupt downloads).
Additionally, those sources shouldn't change regularly (if you're doing
local development like this, please use "pmbootstrap build --src"!)

Enable this option by default, it doesn't introduce any additional risk.
[message trimmed]

[PATCH pmbootstrap v3 0/2] Local development improvements 11 months ago

From Caleb Connolly to ~postmarketos/pmbootstrap-devel

Introdce support for automatically bumping the checksum of local
sources, and for doing "dirty" builds of packages with a custom version
number when there are local changes.

See the individual commit messages for more info.

---
Changes in v3:
- Fix build
- Link to v2: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C20230813-b4-auto-checksum-v2-0-c36231f007b0@postmarketos.org%3E

Changes in v2:
- Don't create a backup file
- Add the new --dirty flag patch

[PATCH pmbootstrap v2 2/2] pmb.build: add a dirty-build feature for local development 11 months ago

From Caleb Connolly to ~postmarketos/pmbootstrap-devel

With automated checksums, the last piece of the puzzle for quick
development of local packages is to fix the pkgver automatically too.
Add a new --dirty flag to pmbootstrap build which will append the current
datetime to the pkgver. This has two main purposes:
1. Ensures that the newly built package will get picked up by apk
2. Makes it clear that the package is from a local "dirty" build and not
from any binary repo.

The dirty flag only applies when either the local checksums are out of
date, or if the local package source dir has been modified since the
last build. This ensures that only packages the user is working on will
get built when this flag is set.

With this logic in place, it is now sensible to add a '--build' flag to
[message trimmed]

[PATCH pmbootstrap v2 1/2] pmb.build: fix local checksums automatically 11 months ago

From Caleb Connolly to ~postmarketos/pmbootstrap-devel

Add a new "auto_checksum" config option which, when set, will make
pmbootstrap fix checksums for local sources in-place before building a
package.

This _drastically_ speeds up development when working with files that
are local to pmaports.

It isn't done automatically for remote sources as there is still some
value in having these error out (e.g. catching corrupt downloads).
Additionally, those sources shouldn't change regularly (if you're doing
local development like this, please use "pmbootstrap build --src"!)

Enable this option by default, it doesn't introduce any additional risk.
[message trimmed]