From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] RIP lafilefixer: I must have missed the memo
Date: Wed, 18 May 2011 19:09:36 -0700 [thread overview]
Message-ID: <BANLkTi=oMh=_dw+j2ckJJoemGshDtxVhrw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
I've been using dev-util/lafilefixer ever since I learned about it. Now
I've bumped into a thread whose latest posts suggests that it is now
obsolete, with a better capability built into portage.
I hope this is true. I'd love to ditch it because "lafilefixer --justfixit"
never fails to process some packages that are hardwired for one reason or
another. Some search engine results suggest this may be true, but they're
mostly old. Is this still and permanently true?
If so, why is it still in portage and no mention of its obsolesence in the
elogs?
--
Kevin O'Gorman, PhD
[-- Attachment #2: Type: text/html, Size: 659 bytes --]
next reply other threads:[~2011-05-19 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 2:09 Kevin O'Gorman [this message]
2011-05-19 8:14 ` [gentoo-user] RIP lafilefixer: I must have missed the memo Sebastian Beßler
2011-05-19 14:23 ` Paul Hartman
2011-05-19 14:44 ` Kevin O'Gorman
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='BANLkTi=oMh=_dw+j2ckJJoemGshDtxVhrw@mail.gmail.com' \
--to=kogorman@gmail.com \
--cc=gentoo-user@lists.gentoo.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