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

Autoclean instead of clean, fix bug with unpacking(Fix #63 and #64) #65

Merged
merged 3 commits into from
Dec 23, 2019

Conversation

EternityForest
Copy link

@EternityForest EternityForest commented Dec 18, 2019

Fixes bugs:

#63 : unpack would chown the enture target dir with all existing files, and
#64 : apt-get clean would delete cached files that are still usable, eliminating caching between builds.

My simple solution for copying files involves unnecessary disk activity, but I think the bug is big enough to warrant fixing sooner rather than later, and then refining as time allows.

@guysoft
Copy link
Owner

guysoft commented Dec 19, 2019

Hey, so two things.
The unpack solution looks good. Worth merging.

Regarding the apt-clean, I think its worth adding an if there, and run autoclean if:

if [ -n "$BASE_APT_CACHE" ] && [ "$BASE_APT_CACHE" != "no" ]; then
  apt-get autoclean
else
  apt-get clean
fi

Do you want to update your branch? I can do it too but rather you have the commit author under you.

Because you want it to clean if you are not using a cache that is binded from outside.

@EternityForest
Copy link
Author

EternityForest commented Dec 20, 2019

Thank you for the feedback! I didn't know you supported non-bound caches.

I will update my branch accordingly!

@EternityForest
Copy link
Author

Branch updated!

@guysoft guysoft merged commit 98426f2 into guysoft:devel Dec 23, 2019
@guysoft
Copy link
Owner

guysoft commented Jan 15, 2020

Hey, I think this merge has effected the super large build at @zynthian which needs an extra of 10GB of storage. cc @jofemodo

I tried increasing the disk size there even further to see if that helps.

@jofemodo
Copy link
Contributor

I must suppose the extra 10GB space we need is inside the SD image. This is a big problem for us ...
How can we solve it? Should we omit the CustomPiOS file copy mechanism and implement our own copy process, after the CustomPiOS finished?

@jofemodo
Copy link
Contributor

jofemodo commented Jan 15, 2020

Does exist a mechanism to prevent the image zip compression at the end of the CustomPiOS process?

@guysoft
Copy link
Owner

guysoft commented Jan 15, 2020 via email

@EternityForest
Copy link
Author

EternityForest commented Jan 15, 2020 via email

@jofemodo
Copy link
Contributor

jofemodo commented Jan 15, 2020

Done! => #66

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

Successfully merging this pull request may close these issues.

3 participants