Thread: kobopatch - An improved patching system
View Single Post
Old 07-17-2018, 12:37 PM   #136
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,257
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by jcn363 View Post
Could we pass the device as a parameter or use a variable?

Spoiler:
Code:
./bin/kobopatch-linux-64bit AuraOne

  vars:
    device: AuraOne

  Parameters:
    DevType:
      Description: Device type.
      Default: AuraOne
      Type: String
      AllowedValues:
        - Touch # Trilogy
        - Touch2 # Pika
        - Mini # Pixie
        - AuraHD # Dragon
        - Aura # Phoenix
        - Glo # uses the values of Phoenix
        - H2O # uses the values of Dragon
        - GloHD # Alyssum
        - ClaraHD # Nova
        - AuraOne # Daylight
      ConstraintDescription: must specify a value.
I've got 4 different models which I'm still patching every fw update. That sounds like I'd need 4 different configurations instead of the single one I currently have. It sounds like more work.
jackie_w is offline   Reply With Quote