public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Craig Ringer <craig@2ndquadrant.com>
Cc: systemtap@sourceware.org
Subject: Re: Newbie Notes
Date: Fri, 08 Nov 2019 12:03:00 -0000	[thread overview]
Message-ID: <20191108120338.GA22271@redhat.com> (raw)
In-Reply-To: <CAMsr+YENsoK3jpyHKmdLd_Xz561mrCFu=eqy9+thu-4ba7Fh0w@mail.gmail.com>

Hi -

> Aha. Makes sense.
> 
> I can work around the PATH issues with @var etc by generating a .tapm
> script with the paths templated in, then use that in a tapset that defines
> the probe aliases etc.
> 
> That'll work well enough that I think I can prepare a usable tapset for
> PostgreSQL.

And if that tapset is in a tapset directory, then the unused var
warnings won't be an issue.


> > OK, working on this bug.
> 
> Cool. I dug through a fair bit of code without figuring it out, sorry :S
> Want me to open a github issue?

Nah, already fixed it last night.  (We use sourceware.org/bugzilla.)

> [...]
> I'll be stuck being backward compatible for a while so I had to work around
> it anyway...

Fair enough.  When we release a new version, we do plop it onto as
many old platform versions as we can.  So fedora30 etc. should get it,
within a few weeks.


- FChE

  reply	other threads:[~2019-11-08 12:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28  7:19 Craig Ringer
2019-10-28  8:55 ` Craig Ringer
2019-10-30 20:10 ` Frank Ch. Eigler
2019-10-31 14:01   ` Craig Ringer
2019-11-07 18:52     ` Frank Ch. Eigler
2019-11-08  4:15       ` Craig Ringer
2019-11-08 12:03         ` Frank Ch. Eigler [this message]
2019-11-10  5:05           ` Craig Ringer

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=20191108120338.GA22271@redhat.com \
    --to=fche@redhat.com \
    --cc=craig@2ndquadrant.com \
    --cc=systemtap@sourceware.org \
    /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).