public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Eray Ozkural <erayo@cs.bilkent.edu.tr>
To: "Mike A. Harris" <mharris@opensourceadvocate.org>
Cc: Syd Polk <spolk@redhat.com>, sourcenav@sources.redhat.com
Subject: Re: sourcenav deb dir layout
Date: Wed, 18 Oct 2000 08:39:00 -0000	[thread overview]
Message-ID: <39EDA593.8ACFA13C@cs.bilkent.edu.tr> (raw)
In-Reply-To: <Pine.LNX.4.21.0010180247550.859-100000@asdf.capslock.lan>

"Mike A. Harris" wrote:
> 
> 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.
> 

Yeah, but deb packages strictly follow FHS compliance. It's a bug
if they don't. :)

> 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)
> 

burgh, a hacked grep? oh, no. i hadn't noticed that.

> 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.
> 

All right, I'm approaching a real package. just a couple of more
fixes, and I'm sending them to you.

> 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?
> 

Yep, I'm always trying to make a minimal number of changes (so
I can maintain them), I'll send you the changes as well.


Cheers,

-- 
Eray (exa) Ozkural
Comp. Sci. Dept., Bilkent University, Ankara
e-mail: erayo@cs.bilkent.edu.tr
www: http://www.cs.bilkent.edu.tr/~erayo

  parent reply	other threads:[~2000-10-18  8:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-17  9:31 Eray 'exa' Ozkural
2000-10-17 10:39 ` Syd Polk
2000-10-17 17:01   ` Eray Ozkural
2000-10-17 17:58     ` Syd Polk
2000-10-17 23:57       ` Mike A. Harris
2000-10-18  0:16         ` Ben Elliston
2000-10-18  0:27           ` Mo DeJong
2000-10-18  8:47             ` Eray Ozkural
2000-10-18 11:16               ` Syd Polk
2000-10-18 12:37             ` Syd Polk
2000-10-18 14:32               ` Ben Elliston
2000-10-18  0:30           ` Mike A. Harris
2000-10-18  8:39         ` Syd Polk
2000-10-18 10:21           ` Mike A. Harris
2000-10-18  8:39         ` Eray Ozkural [this message]
2000-10-18 11:16           ` Syd Polk
2000-10-18 12:14             ` Eray Ozkural
2000-10-18 13:50             ` Mike A. Harris
2000-10-17 23:45 ` Mike A. Harris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39EDA593.8ACFA13C@cs.bilkent.edu.tr \
    --to=erayo@cs.bilkent.edu.tr \
    --cc=mharris@opensourceadvocate.org \
    --cc=sourcenav@sources.redhat.com \
    --cc=spolk@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).