Skip to content
Snippets Groups Projects
Select Git revision
  • 9356bc0f5cc654a6930c164a5df9ef6d10269fef
  • main default protected
  • v0.10
  • 0.10.6
  • 0.10.5
  • 0.10.4
  • 0.10.3
  • 0.10.2
  • 0.10.1
  • 0.10.0
  • 0.9.1
  • 0.9.0
12 results

wpinit

  • Bartek Jaskulski's avatar
    b30935d1
    feat: reintroduce command to compile plugin info · b30935d1
    Bartek Jaskulski authored
    
    Actually, it's better to compile plugin info at build time, because
    later, when client updates the plugin it may be hard to determine
    whether cached file with plugin info should be
    invalidated. Hypothetically, if client has plugin in version 1.0.0, and
    updates to 1.0.1, there's nothing that could tell us, the plugin info
    file is old. The only option would be to read the file and parse headers
    every time, what would defy the cached file purpose. It's just easier
    this way, especially when considering container compilation, which also
    have to be version aware, to make sure only the recent version is used
    for compilation.
    
    Signed-off-by: default avatarBart Jaskulski <bjaskulski@protonmail.com>
    Verified
    b30935d1
    History
    feat: reintroduce command to compile plugin info
    Bartek Jaskulski authored
    
    Actually, it's better to compile plugin info at build time, because
    later, when client updates the plugin it may be hard to determine
    whether cached file with plugin info should be
    invalidated. Hypothetically, if client has plugin in version 1.0.0, and
    updates to 1.0.1, there's nothing that could tell us, the plugin info
    file is old. The only option would be to read the file and parse headers
    every time, what would defy the cached file purpose. It's just easier
    this way, especially when considering container compilation, which also
    have to be version aware, to make sure only the recent version is used
    for compilation.
    
    Signed-off-by: default avatarBart Jaskulski <bjaskulski@protonmail.com>