From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Mike A. Harris" To: Syd Polk Cc: erayo@cs.bilkent.edu.tr, sourcenav@sources.redhat.com Subject: Re: sourcenav deb dir layout Date: Tue, 17 Oct 2000 23:57:00 -0000 Message-id: References: <4.2.0.58.20001017175902.01a3b730@pop.cygnus.com> X-SW-Source: 2000-q4/msg00097.html On Tue, 17 Oct 2000, Syd Polk wrote: >>i don't know where to put sdk, since sdk is not specific to sourcenav? >>if it is specific to sourcenav, then it also goes under share/sourcenav >>it looks like read only arch-independent data. >> >>Cheers, > >Source-Navigator is designed to integrated with the other gnu tools that >Red Hat offers, and has a directory structure which maps that. We will keep >these changes in mind, however. The funny thing though, is Source Navigator doesn't follow Red Hat conventions of file locations either. ;o) Red Hat 7.0 of course approaches FHS compliance, and both debian and Red Hat are becoming similar in this manner. The reason I'm pointing this out is because I am trying to package Source Navigator for Red Hat right now, and having similar difficulties. ;o) The default install of a source nav build scatters files in odd locations as I found out the hard way.. ;o) I had it build for /usr/local, and after installing had numerous problems as an ordinary user on my system. Root, everything worked fine, but as a user, I had different problems running scripts, etc.. It turns out, source nav installs grep/egrep/fgrep and a slew of other utils into /usr/local/bin when built for /usr/local, and /usr/local was in the path first, so the sourcenav utils got used instead of /bin/grep, etc.. The problem is that the SourceNav grep and friends do not support all grep commandline options. It took me a few days to figure this out.. ;o) What is the reasoning behind bringing a copy of grep and other utils with sourcenav? Is it for systems not having it? If so, can I safely exclude it from the Red Hat packages? To the fellow creating the deb packages, could you post your deb build files, (not the packages, just the deb equiv of .spec files) to me privately. I'll share my .spec with you as well if you like. Perhaps we could take some of the changes that will be necessary in the build sections of our efforts and incorporate them directly into the Sourcenav makefiles, etc. and send patches in? Well, one thing at a time I suppose. ;o) Take care everyone! TTYL ---------------------------------------------------------------------- Mike A. Harris - Linux advocate - Open source advocate Computer Consultant - Capslock Consulting Copyright 2000 all rights reserved ---------------------------------------------------------------------- "If it isn't source, it isn't software." -- NASA