From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: Xorg-server-1.14.1.901 Fails Emerge
Date: Thu, 6 Jun 2013 04:16:50 +0000 (UTC) [thread overview]
Message-ID: <pan$78f33$1567fda3$6e345b2d$60ce15a3@cox.net> (raw)
In-Reply-To: 51AF01FB.4090702@gmail.com
Dale posted on Wed, 05 Jun 2013 04:16:43 -0500 as excerpted:
> ebuild path/to/ebuild manifest/digest
>
> Naturally that is from memory and replace the relevant parts. You may
> need manifest for one or digest but structure is the same. Actually, I
> think they both do the same thing after a quick glance at man ebuild.
> Should get you started tho.
That's correct.
Manifest/digest do the same thing now, but years ago there was one
version of it, then things changed a bit and the other appeared that did
something a bit different, but on repositories/overlays using the newer
version the older version simply aliased to the new so people's scripts,
etc, didn't break. I've forgotten the exact details, but I remember it
feeling slightly ridiculous at first using the old form for the new
function, since it wasn't really technically accurate any more. I think
that's why they changed the name on the second, making it more accurate
again. But then that broke people's scripts so they aliased the old to
the new, and now they both do the same thing.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-06-06 4:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 2:17 [gentoo-amd64] Xorg-server-1.14.1.901 Fails Emerge Frank Peters
2013-06-05 6:00 ` [gentoo-amd64] " Duncan
2013-06-05 7:25 ` Frank Peters
2013-06-05 8:03 ` Frank Peters
2013-06-05 8:43 ` Frank Peters
2013-06-05 9:16 ` Dale
2013-06-06 4:16 ` Duncan [this message]
2013-06-06 5:26 ` Duncan
2013-06-06 13:52 ` David Klann
2013-06-05 13:00 ` Rich Freeman
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='pan$78f33$1567fda3$6e345b2d$60ce15a3@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@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