As long as this change is limited to the source tarball created for
archives - +1
On Jan 21, 2008, at 5:14 PM, Jared Rhine wrote:
In our instructions for creating a Chandler build is this step:
Tar it up (on paniolo, as builder):
* tar czf Chandler_src_<tag name>.tar.gz chandler hardhat
external internal
I was wondering about how this relates to the modern "untar into
your directory" standard popularized by GNU software in the 90's.
That is, instead of "tar zxf" creating 4 directories "chandler,
hardhat, external, and internal", should it instead create a single
directory "chandler-<version>" with 4 subdirectories under that
single directory? One could probably find an online rant or two
against software that doesn't "untar into its own directory", but
you either believe that or your don't.
I don't know for sure whether this source tarball is used by any of
our infrastructure (or other's infrastructure); obviously anything
which relies on the 4 subdirectory structure will break if we change
how our source tarballs are made.
Overall, I'm in favor of the change if there are no -1s, flags, or
other such concerns. I'm also in favor of lowercase filenames, now
that I look at it.
-- Jared
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
--
bear
Build and Release Engineer
Open Source Applications Foundation (OSAF)
[EMAIL PROTECTED]
http://www.osafoundation.org
[EMAIL PROTECTED]
http://code-bear.com
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
