Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log the Buildozer.spec delta #1743

Open
Julian-O opened this issue Nov 23, 2023 · 0 comments
Open

Log the Buildozer.spec delta #1743

Julian-O opened this issue Nov 23, 2023 · 0 comments

Comments

@Julian-O
Copy link
Contributor

New feature suggestion:

In bug reports and support requests, we often ask for the Buildozer build logs, and also a copy of the Buildozer spec.

We don't need to ask for a copy of the environment variables, because they are automatically included in the log if the build fails.

My suggestion is to also include the Buildozer.spec in the logs.

But the Buildozer.spec tends to be a long document. It can be difficult to quickly see the few changes the user has made.

Therefore, I propose that what is logged is merely the differences - the default.spec should be loaded in as a ConfigParser instance, and Buildozer should iterate over the two instances looking for changes (modifications, deletions and additions) and just include those in the log.

For most projects, this list is likely to be short; if it isn't, that is likely to be pertinent.

@Julian-O Julian-O changed the title Log the Build.spec delta Log the Builddozer.spec delta Nov 23, 2023
@Julian-O Julian-O changed the title Log the Builddozer.spec delta Log the Buildozer.spec delta Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant