Project

General

Profile

Actions

Feature #962

closed

Add system package to identify platform

Added by Hammel over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Immediate
Assignee:
Category:
07 - opkg
Target version:
Start date:
02 May 2023
Due date:
% Done:

100%

Estimated time:
Severity:
01 - Critical

Description

It would be helpful to have a pkg installed that identifies the system that was built.

This can be done by adding a generic package build with command line option to set the system name at build time.

This new package can be called piconf and contain generally useful configuration options. Alternatively, this could be added to pmsui since all system builds include that package.


Related issues

Related to metabuild - Feature #999: Add System type to /etc/pibox-versionClosedHammel02 Jun 2023

Actions
Actions #1

Updated by Hammel about 1 year ago

  • Related to Feature #999: Add System type to /etc/pibox-version added
Actions #2

Updated by Hammel about 1 year ago

  • Priority changed from Urgent to Immediate
  • Severity changed from 02 - High to 01 - Critical
Actions #3

Updated by Hammel about 1 year ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

This basically the same thing that xeoncfg does for Xeon builds. So I can just duplicate that repo as piconf.

The metabuild can then add this package to each system, passing in a variable that sets the system, as in

  make SYSTEM=<system> pkg

This will require build.sh checking for a token in the build command (re: [MODE]) that can be replaced by the -m value (re: $MODE).

Actions #4

Updated by Hammel about 1 year ago

  • % Done changed from 10 to 30

meta2 has an updated build.sh ready to test against a piconf package. It's been tested against xeoncfg just to make sure the cli variable SYSTEM=<> is properly set.

Now I just need to create a piconf package like xeoncfg.

Actions #5

Updated by Hammel about 1 year ago

  • % Done changed from 30 to 60

piconf repo ready to push upstream into new GitLab repo.

After pushing to gitlab I need to add piconf to a system build, say pisentry, and put it onto hardware to make sure it gets installed correctly.

Actions #6

Updated by Hammel about 1 year ago

  • Status changed from In Progress to Closed
  • % Done changed from 60 to 100

Tested under meta4 against pisentry on hardware and it looks good.
Added piconf to all system build pkglists in meta repo.

Changes committed and pushed.

Closing issue.

Actions

Also available in: Atom PDF