Then you package them differently to address the naming. It’s not rocket science.
If there are two people named “Tom” in a room, do you just give up and walk out of said room because it’s impossible to find a way to communicate in a room with two people of a similar name? No.
No, but its like you expect your Milk to be in the fridge but its not there, but instead someone put it in the fridge of your neighbour for whatever reason. Why would you look there?
Then you package them differently to address the naming. It’s not rocket science.
If there are two people named “Tom” in a room, do you just give up and walk out of said room because it’s impossible to find a way to communicate in a room with two people of a similar name? No.
No, but its like you expect your Milk to be in the fridge but its not there, but instead someone put it in the fridge of your neighbour for whatever reason. Why would you look there?
Ever dealt with packaging files? You tell them where to go. It’s a simple manifest that says where files get unzipped and put on the filesystem.
You have zero idea WTF you’re talking about.
And how does this work when you expect a binary of someone else’s package in a certain location?
Are you trolling or what?
Lolz, are you joking?
No. But you seem to be. I think you have a weird sense of humor.
No I haven’t dealt with packaging files. But packaging files implies that you know where your files are.
But as I stated it’s not about your own files but files from someone else you rely on.
Imagine what havok you would cause when someone things it would be a great idea to put
lsorloginno longer in/binbut/sbininstead?