Trans
1/31/2007 7:31:00 PM
On Jan 31, 1:59 pm, Eric Hodel <drbr...@segment7.net> wrote:
> On Jan 31, 2007, at 02:35, Trans wrote:
>
> > On Jan 31, 4:28 am, Eric Hodel <drbr...@segment7.net> wrote:
> >> On Jan 31, 2007, at 24:40, Trans wrote:
>
> >>> When using the GemPackageTask, one has to build the GemSpec in order
> >>> to define the task. For a large project and/or slow machine this
> >>> actualy can take a second or so.
>
> >>> spec = Gem::Specification.new do |s|
> >>> s.files = FileList.new('**/*').to_a
>
> >> How many files do you have?
>
> > 1,530
>
> Scanning 1500 files is your time sink.
That is obvious. But not the point. Rake doesn't need to scan these
files every time rake is run, only when the package task is run --and
that's what I'm suggesting as an improvement to the task. Clearly the
noticablity of this delay and CPU cycle waste is not largely
discernable to those with small projects and/or faster computers, but
why would that disclude an improvement to Rake's GempackageTask? That
seems to be what you are suggesting.
> >> I solve this by using a Manifest.txt, that way I know exactly what I
> >> want is included, and nothing I don't:
>
> > It's not an issue of knowing what is included. It is a matter of
> > efficency.
>
> Its both. Since I have to verify what I've added to the Manifest.txt
> and check it in, files won't mysteriously appear in my releases that
> shouldn't have been there.
>
> >> s.files = File.read('Manifest.txt').split
>
> >> Plus the check_manifest task from Hoe to make sure everything is up-
> >> to-date.
>
> > What does Hoe do to check the manifest?
>
> A Find.find followed by a diff. If you like the changes, you can
> pipe it to patch.
I see. Thanks.
T.