macdoor commented on code in PR #18036: URL: https://github.com/apache/dolphinscheduler/pull/18036#discussion_r2924368956
########## dolphinscheduler-dist/src/main/assembly/assembly-plugins.sh: ########## @@ -77,8 +77,8 @@ done # create symbolic link for standalone-server cd $BIN_DIR/standalone-server && ln -s ../tools/sql/sql sql -# repack bin tar +# repack bin tar (exclude macOS junk so extraction on Linux is clean) BIN_TAR_FILE_NAME=$(basename $BIN_TAR_FILE) -cd $DIST_DIR && tar -zcf $BIN_TAR_FILE_NAME apache-dolphinscheduler-*-bin +cd $DIST_DIR && tar -zcf $BIN_TAR_FILE_NAME --exclude='._*' --exclude='.DS_Store' apache-dolphinscheduler-*-bin Review Comment: > This is caused by you open the directory by finder? Hi @ruanwenjun, The root cause of this issue is macOS `tar` (bsdtar) behavior — it automatically embeds `._*` (AppleDouble) entries and extended attribute headers into the archive when **creating** a tarball, even if no `._*` files exist on disk. This is a well-known cross-platform issue: https://superuser.com/questions/61185/why-do-i-get-files-like-foo-in-my-tarball-on-os-x > OS X's tar uses the AppleDouble format to store extended attributes and ACLs. [...] You can tell tar to not include the metadata by setting `COPYFILE_DISABLE` to some value. So it's not caused by opening the directory in Finder — it happens whenever macOS bsdtar packs any file that has extended attributes (which macOS adds silently, e.g. `com.apple.provenance`). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
