Charles Wilson wrote:
James R. Phillips wrote:
Interesting idea. I didn't know you could force
configure/make/install to
produce log files.
Wouldn't it be better to produce a separate compressed log file archive,
distinct from the source archive? The contents of the source archive
have bee
On Mon, 10 Oct 2005, Dr. Volker Zell wrote:
> > Igor Pechtchanski writes:
>
> > I feel I should clarify the statement that "I'd rather not pollute the
> > source directory with more files". I don't care if there are extra
> > files in /usr/src/PKG-VER -- that's what it's there for. However,
> Igor Pechtchanski writes:
> I feel I should clarify the statement that "I'd rather not pollute the
> source directory with more files". I don't care if there are extra files
> in /usr/src/PKG-VER -- that's what it's there for. However, I'd rather
> not have 4 extra files pe
On Sun, 9 Oct 2005, Lapo Luchini wrote:
> Igor Pechtchanski wrote:
>
> >You can put them in the package root, or create a
> >"logs" subdirectory -- the structure is up to you.
>
> Or maybe ".logs", for consistence with .build and friends.
> In this case the only "strange" directory "without dot" w
Igor Pechtchanski wrote:
>You can put them in the package root, or create a
>"logs" subdirectory -- the structure is up to you.
>
Or maybe ".logs", for consistence with .build and friends.
In this case the only "strange" directory "without dot" would be
CYGWIN-PATCHES, whose position I don't parti
On Sun, 9 Oct 2005, Dr. Volker Zell wrote:
> > Igor Pechtchanski writes:
>
> > Also, please make sure your ChangeLog is formatted properly, and please
> > attach the patch instead of including it inline.
>
> Ok, here it is.
>
> 2005-09-10 Dr. Volker Zell
>
> * templates/generic-build-
On Sun, 9 Oct 2005, Lapo Luchini wrote:
> Igor Pechtchanski wrote:
>
> >I would compress the log files -- they're only there for reference
>
> Mhh, but aren't they compressed in the -src.bz2 archive itself, anyway?
> I don't quite see the reason to compress them "again", but well, a nice
> idea in
Igor Pechtchanski wrote:
>I would compress the log files -- they're only there for reference
>
Mhh, but aren't they compressed in the -src.bz2 archive itself, anyway?
I don't quite see the reason to compress them "again", but well, a nice
idea in any case =)
--
Lapo Luchini
[EMAIL PROTECTED] (Op
> Igor Pechtchanski writes:
> Also, please make sure your ChangeLog is formatted properly, and please
> attach the patch instead of including it inline.
Ok, here it is.
2005-09-10 Dr. Volker Zell <[EMAIL PROTECTED]>
* templates/generic-build-script (log_pkg_name): New.
> Igor Pechtchanski writes:
> I would compress the log files -- they're only there for reference, and
> place them in a separate archive (again, as James suggested).
Something like
texi2html-1.76-2-src.tar.bz2
texi2html-1.76.tar.gz
texi2html-1.76-2.patch
texi2html-1.76-2.sh
t
> Charles Wilson writes:
> I wouldn't worry about that. See ncurses-X.Y-Z-src.tar.bz2 FWIW,
> I think this is a neat idea (and CAPS help distinguish these files
> from the "working" ones like .patch, .sh, etc).
That was my intention.
> Chuck
Ciao
Volker
> James R Phillips writes:
> Wouldn't it be better to produce a separate compressed log file archive,
> distinct from the source archive? The contents of the source archive
have been
> previously specified.
I don't think so, we just get more information on top on what we already
James R. Phillips wrote:
Interesting idea. I didn't know you could force configure/make/install to
produce log files.
Wouldn't it be better to produce a separate compressed log file archive,
distinct from the source archive? The contents of the source archive have been
previously specified.
On Fri, 7 Oct 2005, Dr. Volker Zell wrote:
> Hi
>
> Sometimes during package reviews it would be useful to have the logs of
> the original configure/make/check/install stage when the package was
> build, but also for comparison between different versions. The patch
> below for the g-b-s saves thes
--- "Dr. Volker Zell" wrote:
> Hi
>
> Sometimes during package reviews it would be useful to have the logs of the
> original configure/make/check/install stage when the package was build,
> but also for comparison between different versions. The patch below for the
> g-b-s
> saves these logfiles
Hi
Sometimes during package reviews it would be useful to have the logs of the
original configure/make/check/install stage when the package was build,
but also for comparison between different versions. The patch below for the
g-b-s
saves these logfiles in the src archive during the spkg stage
F
16 matches
Mail list logo
