public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: egcs@cygnus.com
Cc: Jim Wilson <wilson@cygnus.com>
Subject: Re: problems building on Solaris
Date: Sat, 11 Apr 1998 12:22:00 -0000	[thread overview]
Message-ID: <Pine.GSO.3.96.980411211657.3126C-100000@alcyone.dbai.tuwien.ac.at> (raw)
In-Reply-To: <199804082014.NAA03525@rtl.cygnus.com>

On Wed, 8 Apr 1998, Jim Wilson wrote:
> I see three possible solutions to this problem:
> 1) Add the requirement that people using CVS must install GNU xgettext, and
>    fix snapshots and diffs so that they include the generated .pot files.

I believe this shouldn't become a requirement.

Of course there have been some troubles with generate files in CVS
lately but we shouldn't make it too difficult for people to make use
of CVS snapshots by requiring too many further packages...

> 2) Add the .pot files to the CVS archive.
> 3) Stop building the po subdirectory.
> 
> Personally, I like the last choice.  Here is the patch I have been using,
> but as yet I haven't tried to force this on everyone else.

Either one of 2) and 3) would be fine for me, though 3) will probably
cause less troubles in the long term.

Gerald
-- 
Gerald Pfeifer (Jerry)      Vienna University of Technology
pfeifer@dbai.tuwien.ac.at   http://www.dbai.tuwien.ac.at/~pfeifer/


  reply	other threads:[~1998-04-11 12:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-08  9:27 Richard Gorton
1998-04-08 23:35 ` Jim Wilson
1998-04-11 12:22   ` Gerald Pfeifer [this message]
1998-04-09  3:09 ` Kriang Lerdsuwanakij
  -- strict thread matches above, loose matches on Subject: below --
1998-04-06  8:26 SXTHREE
1998-04-07 19:34 ` Jim Wilson

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=Pine.GSO.3.96.980411211657.3126C-100000@alcyone.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=egcs@cygnus.com \
    --cc=wilson@cygnus.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).