Hallo Patrick, Du schriebst am Fri, 11 Jan 2013 11:18:47 -0500:
> Recompiling msearrayutils, checksum changed for msetypes. ^^ _That_ shouldn't happen. Is it certain that this _was_ compiled before? Or was this the first time this unit was compiled, because it wasn't used before? > And then it cannot write to the /usr/lib/mseide-msegui/.. folder as it > is owned by root. _All_ the system units should be compiled during installation, and thenafter no further compilation should be neccessary except for updates. That way, the ownership by root shouldn't be a problem. Isn't there a special "build-all" unit provided that just references all the system units to have them compiled, although it doesn't produce any useful code, if any code at all? I mean to remember such a thing with some compiler, but cannot recall which one that might have been. > So if this can happen then I don't think this approach will work. That's true, but it might not even bee completely detrimental, although it might cause some (umpleasant, even) surprises. You could make all source _files_ only root writeable, but world readable, although the _directory_ would be _group_ "users" and writeable for them. This has the drawback to allow any user to _delete_ source files, but they still cannot _modify_ any. They should be able to (re)create compiled unit files, though, should this be required. It might still not work if the compiler attempts to reuse a unit file to be recompiled instead of deleting the old one and creating a new one - I don't know what approach is used by fpc. > I am going to install into the user's home directory and see how that > works. This option should always be possible also, but in this case _all_ files (and directories) will belong to the user himself, so he has every right to peruse them (or have them used by some software - that's the only means he can use these data, anyway). > If someone is installing mseide-msegui then likely they will be doing > the compiling. On a multiuser system, there are basically two different kinds of installation possible: - system wide and thus useable for every "legal" user of the system, and - user owned, thus only managed and used by one specific user, who _might_ decide to make all or part of it accessible to other users - then he will be responsible for maintenance and accessibility, too. There might be a third kind available, like on Linux: - group owned, which gives accessibilty of everything to a group of users, but there has to be someone responsible for preparation and maintenance. (This is really only a variation on the special case of "user owned", where the user decided to make the data available to others as well.) > If we get to a situation where multiple users are compiling then I will > try a different approach. But for now it will be in the user's home > directory. That's the single user installation method. That's ok for a beginning. > Should I make it a hidden or visible folder? Any other thoughts / > suggestions / objections? IMHO everything that's directly needed for building a project (e.g. everything that might appear in a "USES" statement) should be visible, anything only used internally may be hidden. Files that should not be changed by the user could be made read-only even for the user who installed the stuff. This will not hinder later removal, after all. Usually, I discover that I need many things that were deemed "internal only" by some developer, so this classification for _development stuff_ seems of little value to me. But that's just my personal experience. -- (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem) ----------------------------------------------------------- Mit freundlichen Grüßen, S. Schicktanz ----------------------------------------------------------- ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
