quoted from the release note: GNU Parallel 20101222 has been released. It is available for download at: http://ftp.gnu.org/gnu/parallel/ New in this release: * GNU niceload is now part of GNU Parallel. GNU niceload slows down a program if the load average is above a certain limit. * Implemented --tmpdir to buffer standard output and standard error in a different place. * Implemented --load to wait until the load is below a limit before starting another job on that computer. * Implemented --nice set the niceness of jobs running both locally and remotely. * Implemented --dry-run to print the job without running it. * Review with focus on clusters. Thanks to Taylor Gillespie http://www.unixpronews.com/unixpronews-49-20101019GNUParallelSpeedUpProcessingWithMulticoresClusters.html * Review with focus on protein similarity. http://kevinformatics.tumblr.com/post/2142473893/cluster-like-computing-using-gnu-parallel * Review in Spanish. http://gr3p.com/2010/12/gnu-parallel-acelera-tus-scripts-en-linux * Quite a few bug fixes. --END-- sry that I totally forgot about its dependencies on ssh and rsync at that time when i put the first ebuild. GNU parallel uses ssh and rsync as external commands to transfer files to/from remote servers for the distributing feature. I'm not 100% sure which is the better way to introduce those deps because people don't need ssh and rsync as long as they use parallel only locally. Possible ways are: a) add 'network'(or such) USE flag which pulls those deps. b) print messages at pkg_postinst() that will tell users like 'You might want to install openssh and rsync to enable network features'. I took (a) this time. correct me if i'm wrong. Regarding ssh client it seems that parallel can accept other ssh clients than OpenSSH by explicitly specifying a command name and options but i think it's safe to stick to OpenSSH for now. Reproducible: Always
Created attachment 257757 [details] parallel-20101222.ebuild
Created attachment 257762 [details] parallel-20101222.ebuild oops
Those deps are only needed at runtime, but they show up in DEPEND, too. I would nearly choose to have an elog only, but the USE flag is also fine. By the way, upstream won't consider changing the name as they claim that GNU parallel is older than the one in moreutils.
I gradually start to feel adopting a USE flag is a bit overkill. so i propose going simply with elog. (git and rsync also use ssh for some tranfers but no openssh dep in the ebuilds) > By the way, upstream won't consider changing the name as they claim that GNU > parallel is older than the one in moreutils. Is this claim true? Even if so, it sounds harsh for GNU parallel to precede moreutils' because most major distros already have 'parallel' of moreutils.
Created attachment 257878 [details] parallel-20101222.ebuild
Version bumped. Maybe you can prepare an ebuild that renames the man page and binary (take your time). Either you patch the build system or just move the files around in src_install(). Ole claims that some distributions have GNU parallel as default, I have not confirmed it, but moreutils is longer in Portage than GNU parallel.
