Summary: | emerge-delta-rsync removes /usr/portage/profile/packages | ||
---|---|---|---|
Product: | Portage Development | Reporter: | tonich <koprut> |
Component: | Tools | Assignee: | Zac Medico <zmedico> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | tove |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
tonich
2006-05-06 07:30:43 UTC
Well, rsync shouldn't be doing that with --exclude="/packages". I've tested with rsync-2.6.8 and it seems to exclude properly. What version of rsync do you have? Here's the section from the rsync manpage that describes the expected behavior: INCLUDE/EXCLUDE PATTERN RULES if the pattern starts with a / then it is anchored to a particular spot in the hierarchy of files, otherwise it is matched against the end of the pathname. This is similar to a leading ^ in regular expressions. Thus "/foo" would match a file named "foo" at either the "root of the transfer" (for a global rule) or in the merge-file's directory (for a per-directory rule). (In reply to comment #1) > Well, rsync shouldn't be doing that with --exclude="/packages". I've tested > with rsync-2.6.8 and it seems to exclude properly. What version of rsync do > you have? > > Here's the section from the rsync manpage that describes the expected behavior: > > INCLUDE/EXCLUDE PATTERN RULES > > if the pattern starts with a / then it is anchored to a particular spot in the > hierarchy of files, otherwise it is matched against the end of the pathname. > This is similar to a leading ^ in regular expressions. Thus "/foo" would match > a file named "foo" at either the "root of the transfer" (for a global rule) or > in the merge-file's directory (for a per-directory rule). > you right, is not rsync's "--exclude" problem, may be tarsync "${FILE}" "${PORTDIR}" -v -s 1 -o portage -g portage -e /distfiles -e /packages -e /local "-e /packages" |