| 1 |
peter: |
| 2 |
|
| 3 |
> Peter Stuge wrote: |
| 4 |
> > Essentially you will be maintaining a private fork of gentoo.git, |
| 5 |
> |
| 6 |
> If this seems too heavy handed then you can just as well do the reverse: |
| 7 |
> |
| 8 |
> Maintain an overlay repo with the packages you care to control in the |
| 9 |
> state you care to have them, set that in the catalyst stage4.spec |
| 10 |
> portage_overlay and add unwanted package versions in gentoo.git to |
| 11 |
> the package.mask directory used by catalyst. |
| 12 |
> |
| 13 |
> This may sound complicated but it isn't bad at all. |
| 14 |
> |
| 15 |
> For total control also make your own profile, e.g. based on embedded, |
| 16 |
> but that's not per se neccessary, only if the standard profiles has too |
| 17 |
> much conflicts with what you want in @system. |
| 18 |
> |
| 19 |
> catalyst will rebuild @system according to spec file but with too much |
| 20 |
> difference that just becomes annoying and feels more trouble than a |
| 21 |
> controlled profile. |
| 22 |
> |
| 23 |
> This approach falls somewhere between your options (1) and (5). |
| 24 |
|
| 25 |
Wow, wasn't aware of catalyst at all. What a beast in terms of |
| 26 |
control. |
| 27 |
|
| 28 |
(FYI: I enjoyed the links on catalyst you sent me directly. |
| 29 |
Unfortunatelly I cannot answer you directly due to the default TLS |
| 30 |
guarantee kicked in by my provider: "TLS is required, but was not |
| 31 |
offered by host". That's usually to be fixed on the receiving side.) |
| 32 |
|
| 33 |
While being able to build exact environments with catalyst I wonder |
| 34 |
how it could help fixing the issue of my original post. To sum up: |
| 35 |
Whenever we need to deliver a updated app to customers whose OS is |
| 36 |
too old (but updating it is too risky), we could either a) keep |
| 37 |
evenly outdated dev build OSes around forever (oh no!), or b) post |
| 38 |
our newly built app in a container (leaving the lovely native |
| 39 |
world); and both ignore the fact that customers wish maintenance of |
| 40 |
the entire OS actually, too. So, ideally, there is c): In a |
| 41 |
hypothetic case we would prepare a entire OS incl. our app (maybe |
| 42 |
via catalyst?) which would require a bootloader-like mini-OS on the |
| 43 |
customer's side, to receive updates over the internet, switch the OS |
| 44 |
at boot time, and fallback. I was recently playing with systemd-boot |
| 45 |
and it's interesting try-boot feature. |
| 46 |
|
| 47 |
Thanks |
Archives