Re: fire privileges

On 23 Jan, 2005, at 22:15, Jason Townsend wrote:

> My point is if the Finder is able to delete the original when you 
> trash it, it could obviously do the same thing in this case and 
> replace the existing app bundle.
>
> If you are the owner of the original item, you should be able to 
> replace it. Why should that be different than deleting the original 
> and copying in the new?

Because the fact that it's unwritable suggests that you (or whoever 
decided to make it unwritable) don't want it to be overwritten, because 
it's probably accidental, like locked files. But when you move it to 
the trash, you probably know what you're doing.

Even the unforgiving command line doesn't let you rm -Rf unwritable 
directory structures or locked files. Allowing you to delete them with 
'empty trash' is a convenience, so users don't have to change the 
permissions/locked-ness on every file.

> If we were to change the permissions on the app to start with this 
> would only address the issue in the subsequent update since everyone's 
> existing copy of Fire has the current permissions.

Yes, but it's better than leaving the app unwritable, which it 
shouldn't be.

- Purr



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Fire-talk mailing list
[email protected]
To unsubscribe or change your options use the web interface:
https://lists.sourceforge.net/lists/listinfo/fire-talk
Have a question? Please read the Fire Frequently Asked Questions:
http://fire.sourceforge.net/faq.shtml