Re: [dev] deliver's verbosity

2008-06-12 Thread Christian Lohmaier
Hi *,

On Wed, Jun 11, 2008 at 8:56 PM, Pavel Janík <[EMAIL PROTECTED]> wrote:
> On 11.6.2008, at 20:49, Frank Schönheit - Sun Microsystems Germany wrote:
>
>> just noticed that in m18, deliver isn't as gossipy as before: doing a
>> "deliver" in a module just prints
>>  deliver -- version 1.127
>>  Module 'module' delivered successfully. x files copied, y files
>>unchanged.
> ...
>>
>> Is there an option I missed? If not, is there a possibility to introduce
>> one?
>
> VERBOSE=TRUE

Why was it changed again?

I could live with build --deliver as called during a build ist silent,
but deliver called directly was verbose.
What is the rationale behind making deliver itself silent?

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] deliver's verbosity

2008-06-12 Thread Rüdiger Timm



Frank Schönheit - Sun Microsystems Germany wrote:

Hi,

just noticed that in m18, deliver isn't as gossipy as before: doing a
"deliver" in a module just prints
  deliver -- version 1.127
  Module 'module' delivered successfully. x files copied, y files
unchanged.


Yes, that was me on CWS shutup2
http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=6170&OpenOnly=false&Section=Overview
(see also http://blogs.sun.com/GullFOSS/entry/shut_up_or_better_tell ).



While this is nice in contexts where you are not interested in *what*
got actually delivered, it seems there is no way to revert to the old
behaviour: "deliver -help" doesn't list an option to be more verbose
(though it lists "deliver -quiet", which does the same as "deliver",
funnily).

I find this unfortunate, since I sometimes indeed want to know what's
going on, and would be *really* interested which files were actually
delivered.

Is there an option I missed? If not, is there a possibility to introduce
one?


There is a help entry I missed to add, sorry. As others already pointed 
out, option '-verbose' should give you back the old behaviour when 
calling 'deliver' manually. On a global scope you can set an environment 
variable VERBOSE=TRUE, but that also affects some other things.

I'll fix that bug soon.

Rüdiger

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] Urgent:demo applications not building

2008-06-12 Thread Thorsten Behrens
On Wed, Jun 11, 2008 at 11:00:01PM -0700, [EMAIL PROTECTED] wrote:
> (gdb) bt
>
> [snip]
>
> #2  0xb7d6cf51 in uno_type_any_assign ()
>from /2.3.1/OOG680_m9/solver/680/unxlngi6.pro/lib/libuno_cppu.so.3
>
Hm, that's usually the 3-layer-OOo blues - binaries in dev300 build no
longer run without further magic. I tend to copy them into the
openoffice.org3.0/program dir of an existing installation, and
duplicate the sofficerc file (e.g. into canvasdemorc)

HTH,

-- Thorsten

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]