| Summary: | `ebuild ... help` contains outdated help for `ebuild ... digest` | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Arfrever Frehtes Taifersar Arahesis (RETIRED) <arfrever> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | Keywords: | InVCS |
| Priority: | High | ||
| Version: | 2.2 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 216231 | ||
|
Description
Arfrever Frehtes Taifersar Arahesis (RETIRED)
2007-04-14 22:32:52 UTC
Since manifest2, the digest and manifest commands are effectively synonymous, so we should really just update the documentation to reflect that. Currently, the way to disable generation of files/digest-* is to create a file named ${PORTDIR}/manifest1_obsolete (content of the file does not matter). The existence of that file also triggers repoman to remove files/digest-* from cvs. See bug 167667.
(In reply to comment #1) > Currently, the way to disable generation of files/digest-* is to create > a file named ${PORTDIR}/manifest1_obsolete I had known about it before you replied. I just forgot to mention it. Some proof: https://forums.gentoo.org/viewtopic-t-551533-highlight-manifest1_obsolete.html > Since manifest2, the digest and manifest commands are effectively > synonymous, so we should really just update the documentation to reflect > that. Maybe digest command should be marked as deprecated (both in ebuild.1 and `ebuild ... help`). (In reply to comment #2) > Maybe digest command should be marked as deprecated (both in ebuild.1 and > `ebuild ... help`). We can, but I think it will be easier on the users if we just make the 2 commands synonymous. I'm not sure which one people use more, but since they're practically the same, I don't see why we should force users to switch to a different command than the one that they are accustomed to. *portage-2.1.4.1 (01 Feb 2008) 01 Feb 2008; Zac Medico <zmedico@gentoo.org> +portage-2.1.4.1.ebuild: 2.1.4.1 bump. This fixes bugs #138159, #205718, #205966, #206772, and #207104. Bug #200044 tracks all bugs fixed since 2.1.3.x. If you have an overlay then you should remove **/files/digest-* files (Manifest1) because they are no longer supported. If earlier versions of portage will be used to generate manifests for your overlay then you should add a file named manifest1_obsolete to the root of the repository in order to disable generation of the Manifest1 digest files. `ebuild ... help` contains outdated help for `ebuild ... manifest`: Portage Copyright 1999-2006 Gentoo Foundation How to use the ebuild command: The first argument to ebuild should be an existing .ebuild file. One or more of the following options can then be specified. If more than one option is specified, each will be executed in order. help : show this help screen setup : execute package specific setup actions fetch : download source archive(s) and patches digest : create a digest and a manifest file for the package manifest : create a manifest file for the package unpack : unpack/patch sources (auto-fetch if needed) compile : compile sources (auto-fetch/unpack if needed) test : test package (auto-fetch/unpack/compile if needed) preinst : execute pre-install instructions postinst : execute post-install instructions install : install the package to the temporary install directory qmerge : merge image into live filesystem, recording files in db merge : do fetch, unpack, compile, install and qmerge prerm : execute pre-removal instructions postrm : execute post-removal instructions unmerge : remove package from live filesystem config : execute package specific configuration actions package : create a tarball package in /usr/packages/All rpm : build a RedHat RPM package clean : clean up all source and temporary files (In reply to comment #5) > `ebuild ... help` contains outdated help for `ebuild ... manifest`: s/manifest/digest/ Fixed in r9475 and released in sys-apps/portage-2.2_pre5. |