Ok, so I have just completed an intensive update/re-write of one of my software packages, and I am ready to throw it up on my website. The package contains five files, the app itself, a manpage, an install script, a README and a copy of the Artistic License, under which it is released.

My question is what is the best user:group to chown these files to...the last few versions I just left as they are...owned by my user, with UID 1000. It seems to me that if someone downloads this package and they are not UID 1000 they may have permission problems with the files. Same as if I released it with root owning all the files. I need users to be able to use this from their home directory if they don't have root access to the box they are using...

So, what is the correct/preferred way of chowning files to be released to the public?
Does it even matter? When I download source files they seem to be automattically owned as the user I downloaded them as, is there a certain way to see that this happens?

TIA

It doesn't matter because when a user downloads (writes the file to their machine) they are the owner. Make the owner of these files whoever owns the directory they are placed in.

That's what I thought. I'll keep on doing what I was doing then. Thanks for the reply.

You're welcome. I'm pleased I could be of service.