Re: [gentoo-dev] merging man page documentation into eclasses
Mike Frysinger wrote: keeping documentation of functions in a separate file (man pages in this case) has obvious bit rot problems written all over it, so i'd like to merge the documentation into the respective eclasses so that the man pages can be automatically generated +1 Of course, I always use the eclass itself for reference (since not all eclasses have man pages). Cheers Andrew signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] dont use `which` in ebuilds
Ned Ludd wrote: On Mon, 2007-03-12 at 19:15 -0400, Mike Frysinger wrote: On Monday 12 March 2007, Mike Frysinger wrote: instead, since we require bash for our ebuilds, use the builtin `type -p` `type -p` is almost a complete drop in replacement for which ... it does not work on bash builtins however, so people should use `type -P` to force the PATH search Quick search shows the following ebuilds are abusing this behavior. app-emulation/xen-tools/xen-tools-3.0.2-r3.ebuild:57: app-emulation/xen-tools/xen-tools-3.0.2-r4.ebuild:52: Fixed. Cheers Andrew signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] New developer: Christian Marie (pingu)
Petteri Räty wrote: It's my pleasure to introduce to you Christian pingu Marie. He hails from down under. He's living in Australia Does this mean we have an Australian conspiracy starting up? :-) Cheers Andrew signature.asc Description: OpenPGP digital signature
[gentoo-dev] Linking to Gentoo-wiki from www.gentoo.org
Daniel Ostrow wrote: Gentoo-wiki does not now nor will it ever get linked to from official Gentoo media, documentation, or anything else within the www.gentoo.org namespace... Really? http://www.gentoo.org/news/en/gwn/20060424-newsletter.xml http://www.gentoo.org/proj/en/overlays/devguide.xml#doc_chap3 http://www.gentoo.org/doc/en/handbook/draft/complete/handbook.xml?part=1chap=6#doc_chap2 (Yes, it's only a draft, but it still meets your criteria) Mind you, I'm not saying that I agree with linking to Gentoo-wiki - I just think it's important to point out that your statement is incorrect. Cheers Andrew signature.asc Description: OpenPGP digital signature
[gentoo-dev] Linking to Gentoo-wiki from www.gentoo.org
Daniel Ostrow wrote: Gentoo-wiki does not now nor will it ever get linked to from official Gentoo media, documentation, or anything else within the www.gentoo.org namespace... Really? http://www.gentoo.org/news/en/gwn/20060424-newsletter.xml http://www.gentoo.org/proj/en/overlays/devguide.xml#doc_chap3 http://www.gentoo.org/doc/en/handbook/draft/complete/handbook.xml?part=1chap=6#doc_chap2 (Yes, it's only a draft, but it still meets your criteria) Mind you, I'm not saying that I agree with linking to Gentoo-wiki - I just think it's important to point out that your statement is incorrect. Cheers Andrew signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Group limit for NFS exported file systems
Robert Szentmihalyi wrote: is there a group limit for NFS exported file systems in recent kernels? One if my users cannot access directories that belong to a group he actually _is_ a member of. That, however, is true only when accessing them over NFS. On the local file system, everything is fine. UIDs and GIDs are the same on client and server, so that cannot be the problem. Client and server run Gentoo Linux with kernel 2.6.16-gentoo-r9 on the server and 2.6.17-gentoo-r4 on the client. You'll have a better chance of getting an answer to your question on the gentoo-users mailing list, the #gentoo IRC channel on freenode, or an NFS-specific mailing list/IRC channel. Cheers Andrew signature.asc Description: OpenPGP digital signature
[gentoo-dev] Dealing with /var/cache on unmerge
Apologies if this has been addressed previously, but my searches of the Gentoo website, devmanual, forums, and mailing list archives didn't turn up anything definitive. Is there any sort of policy covering how an ebuild should deal with /var/cache during unmerge? The devmanual pages for pkg_prerm (http://tinyurl.com/huh7n) and pkg_postrm (http://tinyurl.com/f5b7o) are the closest I've come to an answer, but I don't consider deletion of the cache dir to be the same as updating it. I've looked at a few ebuilds in the tree (including samba and squid) and they seem to leave in place any cache files created during normal execution of the package in question. This means that after an unmerge the sysadmin needs to go and clean out /var/cache/whatever. During ebuild development and testing, I can see why one might want the cache files to remain, so unconditional cleaning of /var/cache is out of the question. However, removing of cache files could be controlled by a FEATURE (eg. keepcache - unless that implies the retention of cache files from the original merge a la keepwork and keeptemp). A similar issue exists with log files, but I'd expect them to occupy less space than caches, and generally be considered more useful (since they can't be regenerated). If they were to be dealt with, perhaps portage could have a purge option that removes all traces of a package from the system - including log and cache files (it looks like temp files should already be cleaned out by the ebuild). Of course, the general opinion might be that management of /var/cache is outside the scope of portage, and best left to the sysadmin (and/or an separate automated tool), although the FHS doesn't specify either way (http://tinyurl.com/26gpd). That's fine with me, but I think it's good to have this on record in the mailing list archives, and perhaps in the devmanual as well. Cheers Andrew -- gentoo-dev@gentoo.org mailing list
