On Wed, Jun 3, 2009 at 2:23 PM, Hisham <hisham...@gmail.com> wrote: > On Tue, Jun 2, 2009 at 8:32 PM, Michael Homer <mich...@gobolinux.org> wrote: >> On Wed, Jun 3, 2009 at 3:26 AM, Lucas C. Villa Real >> <luca...@gobolinux.org> wrote: >>> On Sat, May 30, 2009 at 5:49 AM, Jonas Karlsson <cj.karls...@gmail.com> >>> wrote: >>>> There are some things I'd like to change in Compile and Scripts for >>>> 015 that may not be optimal to release before that. >>>> First I'd like to change default behaviour of Compile to use >>>> /System/Index. I know this is a big step, but I've had enought >>>> headaches with applications looking for files inside it's own prefix >>>> while it really should search global directories since the actual file >>>> was installed by another application or library. Plugins is a good >>>> example. >>> >>> Yes, I agree with that. We've been postponing that for a few years now >>> and it would be a shame to wait for one more release. I don't really >>> care if 015 is put on hold for a while if the reason is to switch over >>> to /System/Index. >> I do, dependent on what "a while" is. If it's ready now, or even ready >> enough to go on in a preliminary snapshot and be polished up over the >> rest of the release process, then by all means. If it isn't, waiting >> on "just one more feature" (or several one more features, as it turns >> out) isn't worth it. Put it into 016 and release that six months down >> the track, like 015 was supposed to be, and it won't be long to wait. >> >> If something isn't ready now, it should be cut. The release is already >> a year late. Deferring it for blue-sky features is silly when they >> could go into the start of the next release, and not be vapourware. >> >> If it is ready to go however, just put it in already and the rough >> spots can be ironed out later. > > I agree with Michael. I remember Lucas had some trouble when trying to > force all packages to build targeting /System/Index. My suggestion > (which I don't think he followed back then) was to have those build > relative to /Programs as an exception. Consider it something like > "safe linking". If a minority needs it (and they already work fine > under /P) then let's keep those the way they are and let the other > stuff (especially those that are having trouble building in /P, such > as plugin-based apps) be happy with /S/I. > > Also (in a typical anti-dogmatic version), while we're at it, why not > use /usr instead of /System/Index? I know what I wrote in the "I am > not clueless" article, but even then my only strong argument against > it was that it required union filesystems which were not widely > available back then.
Because /usr is ugly. If we rely on it then we should also unhide it from the filesystem view. I feel really disturbed with the idea of "assuming" that directory. -- Lucas "If you're looking for a reason I've a reason to give: pleasure, little treasure" _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
