| « Graphics shuffle | Benchmarks: gtk+ engines » |
December public service announcement
For all the forumites, bloggers, wikifolks, mailing list members, bugzilla commenters, and general Gentoo netizens:
Please stop spreading bad advice such as ebuild foo digest. It does not exist. Digests have not been present in the Portage tree for a year, ever since the tree was converted to Manifest2 format.
If you've made a local modification to an ebuild, patch, or added anything else to your local overlay and need to make Portage aware of the changes so the package can be properly merged, do not use the "digest" command. Use "manifest" instead. For example:
ebuild foo-1.0.17.ebuild manifest
Digests have been dead for a long time. Please don't encourage bad practices.
This has been a December public service announcement. Thank you for flying Gentoo Air, and please enjoy the rest of your Christmas!
Trackback address for this post
Trackback URL (right click and copy shortcut/link location)
10 comments
Comment from: AllenJB [Visitor] · http://allenjb.me.uk
Except it does. It's aliased to manifest so does exactly what people expect. If you want people to stop using it, you're going to have to at the very least display a message when it's used, if not remove it completely.
The digest command is even valid according to the man page:
digest This is now equivalent to the manifest command.
Personally, since it does exactly what people want it to do and is, according to the documentation, a valid command, I don't see how it can be considered a "bad practice" - bad practices are usually things which don't do what people want or are at the very least deprecated (which this command is not marked as)
The digest command is even valid according to the man page:
digest This is now equivalent to the manifest command.
Personally, since it does exactly what people want it to do and is, according to the documentation, a valid command, I don't see how it can be considered a "bad practice" - bad practices are usually things which don't do what people want or are at the very least deprecated (which this command is not marked as)
12/24/08 @ 09:12
There was some discussion awhile ago about removing "digest" entirely since it's nothing more than an alias to "manifest". It is indeed misleading that it's even still in the "ebuild" command, given the fact that digests aren't used anymore. Some of my fellow devs on IRC seemed to agree, so I suppose I'll need to talk to zmedico to get the wording cleared up.
Also, what manpage are you reading? Here's what I have in "man ebuild", for Portage 2.1.4.5:
digest: Creates a digest file for the package in /usr/portage/[category]/[package]/files/. This digest file lists the checksums of all the files found in the SRC_URI. See the --force option if you would like to prevent digests from being assumed. For further information regarding the behavior of this command, see the documentation for the assume-digests value of the FEATURES variable in make.conf(5).
manifest: Updates the manifest file for the package. This performs the second half of the digest command, creating md5sums for the files in the files directory as well as the ebuild.
Also, what manpage are you reading? Here's what I have in "man ebuild", for Portage 2.1.4.5:
digest: Creates a digest file for the package in /usr/portage/[category]/[package]/files/. This digest file lists the checksums of all the files found in the SRC_URI. See the --force option if you would like to prevent digests from being assumed. For further information regarding the behavior of this command, see the documentation for the assume-digests value of the FEATURES variable in make.conf(5).
manifest: Updates the manifest file for the package. This performs the second half of the digest command, creating md5sums for the files in the files directory as well as the ebuild.
12/24/08 @ 10:22
Comment from: AllenJB [Visitor] · http://allenjb.me.uk
Sorry, should've mentioned, the portage 2.2 rc17 man page.
12/24/08 @ 12:53
Comment from: Polynomial-C [Visitor]
At least some warning would be nice. I used "ebuild ... digest" since I started using Gentoo in 2003 and really heard about "ebuild ... manifest" the first time in your blog entry here.
12/24/08 @ 13:59
Comment from: Ben Bennett [Visitor] · http://limey.net/
I have removed the heresy from gentoo-wiki.
12/24/08 @ 14:18
Comment from: Mart Raudsepp [Visitor] · http://planet.gentoo.org/developers/leio
I use digest, not manifest, exclusively while packaging stuff for Gentoo. It is just SO much easier to type in a second, than manifest in three seconds to my typing fingers :P
12/24/08 @ 15:16
I think Mart just made an outstanding case for keeping the current alias behavior. It really does take too long to type out "manifest." I mean, all those extra letters! Who can keep up! :p
12/24/08 @ 23:59
Comment from: Kevin Bowling [Visitor] · http://www.kev009.com/
Are you kidding? It's an alias. BFD. There are a lot more pressing items that need attention than removing a keyword that lots of us use.
I'll go as far as to argue the lexicon. By digesting (processing, summarizing, etc.) you build a manifest(a proof, list,etc.). Either or make sense still.
I'll go as far as to argue the lexicon. By digesting (processing, summarizing, etc.) you build a manifest(a proof, list,etc.). Either or make sense still.
12/25/08 @ 05:45
Comment from: Duncan [Visitor] 
I've been using the manifest command for some time, but I never type it out. That's what tab completion is for! =:^)
In fact, the biggest bother (even with tab completion) is that ebuild takes the full path.
ebuild /full/path/to/cat-egory/pkg/pkg-x.y-rz.ebuild manifest
becomes something like (with * indicating tab):
"eb* /f*pa*t*ca*eg*/pk*/p*y* ma*"
Clearly, the path is much more trouble than the ma* bit.
This of course does require the gentoo-bashcomp package and that it is enabled for completion either system-wise or for your particular user, but surely, anyone worried about typing a few extra chars either already has that merged and enabled or is using a similar solution of their own design.
In fact, the biggest bother (even with tab completion) is that ebuild takes the full path.
ebuild /full/path/to/cat-egory/pkg/pkg-x.y-rz.ebuild manifest
becomes something like (with * indicating tab):
"eb* /f*pa*t*ca*eg*/pk*/p*y* ma*"
Clearly, the path is much more trouble than the ma* bit.
This of course does require the gentoo-bashcomp package and that it is enabled for completion either system-wise or for your particular user, but surely, anyone worried about typing a few extra chars either already has that merged and enabled or is using a similar solution of their own design.
12/25/08 @ 07:40
Comment from: Betelgeuse [Visitor] · http://dev.gentoo.org/~betelgeuse
The best command to use is repoman manifest.
01/01/09 @ 20:47
Comment feed for this post