!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

220 Members
60 Servers

Load older messages


SenderMessageTime
5 Sep 2024
@k900:0upti.meK900But also I'm thinking just hashing the store path might be weird for like locally built things08:29:02
@k900:0upti.meK900We should because we could have a different build of the same Qt version08:29:24
@k900:0upti.meK900With a different struct layout08:29:30
@k900:0upti.meK900That's not guaranteed to be consistent across ABIs etc08:29:43
@outfoxxed:outfoxxed.meoutfoxxedbut there shouldnt be a different struct layout with the same qt version08:29:44
@outfoxxed:outfoxxed.meoutfoxxedimage.png
Download image.png
08:30:01
@outfoxxed:outfoxxed.meoutfoxxedtag is the full git hash08:30:03
@k900:0upti.meK900There can be if it's running like08:30:05
@k900:0upti.meK900aarch64 Qt in qemu-user08:30:11
@k900:0upti.meK900Or some nonsense08:30:12
@outfoxxed:outfoxxed.meoutfoxxeduh i guess technically?08:30:30
@k900:0upti.meK900Basically store path is 100% safe so I think we do store path08:30:31
@k900:0upti.meK900Unless there's strong reasons not to08:30:35
@k900:0upti.meK900Like OK we'll get the cache blown out once a staging cycle08:30:49
@outfoxxed:outfoxxed.meoutfoxxedalright lets drop the patch and just write .tag in preconfigure though08:30:51
@k900:0upti.meK900Is that really a problem08:30:52
@k900:0upti.meK900Agreed08:30:55
@outfoxxed:outfoxxed.meoutfoxxednot as long as its able to clean up08:31:00
@outfoxxed:outfoxxed.meoutfoxxedwhich it can since thats validation not id08:31:10
@k900:0upti.meK900OK so our key structure ends up being (app name, filename hash, ["build-id", mtime])08:33:46
@k900:0upti.meK900Where build-id is either Qt "tag" or hash(Qt "tag" + app store path) depending on whether we're outside of the store or inisde08:34:16
@k900:0upti.meK900And when we're inside the store, mtime is 008:34:28
@k900:0upti.meK900So technically we end up with either (Qt "tag", mtime) or (Qt "tag", app store path)08:34:51
@k900:0upti.meK900And when I spell it out like that it kinda makes more sense to maybe hash the app store path into mtime instead?08:35:04
@outfoxxed:outfoxxed.meoutfoxxedthe only problem with that is you have 8 bits08:35:19
@k900:0upti.meK900Though then we don't have a way to tell if it's a hash or an actual mtime08:35:21
@outfoxxed:outfoxxed.meoutfoxxedinstead of 48 bytes08:35:23
@k900:0upti.meK900Wait is it 8 bits or 8 bytes08:35:28
@outfoxxed:outfoxxed.meoutfoxxedbytes sorry08:35:35
@k900:0upti.meK900I feel like 8 bytes is enough honestly?08:35:56

Show newer messages


Back to Room ListRoom Version: 9