Re: [Astlinux-devel] trouble with build - sha1 checksums don't match

[Lonnie A. <li...@lo...>]

> On May 26, 2019, at 8:33 AM, Bill Lewis <wr...@gm...> wrote:
> 
> On 5/25/2019 6:44 PM, Lonnie Abelbeck wrote:
>> It's an option in 'make menuconfig'.
>> OK, if the packages are not selected in the default configs, ex. astlinux-ast13.config, x86_64-configs/astlinux-ast13se.config, etc. selecting others will not work.
>> 
>> You can *unselect* certain packages, say "zabbix" if you don't want it.
>> 
>> The build system is based on Buildroot and over the years we have been maintaining the packages, but only the packages we use.
>> 
>> Our AstLinux version of Buildroot dots the i's and crosses the t's for the packages we use to do what we do.  If we see a need to add a new package we will, but we don't support packages outside the default configs.
>> 
>> 
>> If you want a generic Buildroot build system you can take a look at: https://buildroot.org/
>> 
>> Lonnie
>> 
>> 
> OK.  Perhaps I didn't read enough, but I didn't know those options weren't connected.

The unused-package options are connected, but contain old versions, URL's, patches, etc. .

We have considered cleaning-up unused packages (removing them) but that effects the .config files for custom builds by our power-users, so we passed on that idea.


> FWIW, I updated the Ruby .mk file to a current version and point to their new download location, and stuck in a fake .sha1 file in the 'dl' directory.  It all built and seems to work.

Cool.
Tip -> if you download a unused-package (auto saved to dl/) you don't need to add a local .sha1 file ... the first time it will display an error that the .sha1 could not be found, but you can then re-run the build and it will "trust" the local dl/ version.

Bill, the AstLinux devs follow the upstream Buildroot commit log to find any changes that may apply to us and apply then to our older Buildroot base.  We return the favor from time to time as well.

Lonnie