Re: [jazzplusplus-devel] Tex2RTF build

[D.B. M. <db...@ho...>]

Greetings,

----------------------------------------
> Date: Sat, 17 May 2008 20:58:35 -0700
> Subject: Re: [jazzplusplus-devel] Tex2RTF build
> 
> PS =Pete Stieber
> PS>> We only use the console or non-GUI version of
> PS>> tex2rtf in our builds so I copy
> PS>> BuildTex2rtf/src/tex2rtf to a bin directory
> PS>> under my wxWidgets installation.
> 
... < snip>...

> PS>> To be "normal" we should have the user type
> PS>> "make install" as root, or use "sudo make install"
> PS>> for distributions that prefer sudo.
> 
> DM> If it's going to go system-wide, yes, they'll need
> DM> root_priv or sudo
> DM>
> DM> If it's only going to be used at compile time
> DM> of Jazz++ buld process, it of course doesn't
> DM> need to go system-wide...
> DM>
> DM> In buildingwx, we use su for install
> DM> in buildingjazz we avoid root_priv
> 
> Correct, but the user would need to specify --prefix=... just like in 
> the Jazz++ build.  I guess we could have them use TestInstall, but all 
> of our (actually your ;-)) current instructions assume a 
> jazzplusplus/trunk/jazz checkout instead of a jazzplusplus check out 
> that would be required to obtain tex2rtf.  We would always require two 
> separate checkouts to achieve this.
> 

...hmmm. Altering the docs is something that doesn't bother me.
(sometimes I think it's more preferable than changing other things)

That said, I possibly think of how many people actually try an svn
co & build overall....right now like. That answer doesn't matter - what
I'm saying is, once people get used to one way of doing things, it's
best not to throw'em a curve ball....(so we take our time here and
don't confuse them and come up with....'the plan'...| -)

I believe the current reality is quite sane, in as much as the current
instructions for an svn build of jazz++ have established a 'this is
how we do it, keeping the svn build stuff 'outside' the system tree
as much as we can....
                               ....for now in these pre-release days, tex2rtf
should probably stay in this created 'bubble'. This way, one uses
pretty much the same configuration stage options for all things
coming from jazz++ svn....
 
....however, you're right when you talk about a separate tarball
release of tex2rtf itself. If this were the case, I would ask ;

Does the svn build *really* need a tex2rtf linked against the
custom-wx build libs to give us the functionality (of tex2rtf)
we need (for the jazz++ build process)?

If not, then  for sure  a release of tex2rtf should be made 
available ASAP. Then it really *is* 'normal'...ie; download,
unpack, ./configure --prefix=/usr ; make ; su make install
et_voila. It'll link against user's system wx-libs, be in $PATH
and become a small dependency of jazz++ itself. Of course,
if we can get binary packages of this happening, then all
the better....

Imagining a time when you had the time to make tex2rtf 
a project of it's own, that's no big deal to link across
to (if you ever find that time ;-)...and remember, we do
have the tex2rtf page to assert all this to the world, and
something like "going to be a project of it's own one day
when I get time to work on it more, but for now a 
functional tarball of this utility is being released on
the sourceforge download area for jazz++'..blabla, works
for me... 

> DM> Going by your outlay here, the process should
> DM> be wx->tex2rtf->jazz++
> 
> Correct.  wx is required for tex2rtf.  Both wx and tex2rtf are required 
> for Jazz++.
> 
> DM> Is the plan to have a *release* tarball with all
> DM> this automated?
> 
> The release tarball for Jazz++ will not include any tex2rtf stuff other 
> than the help files it generates.  We may want to generate a separate 
> tarball for tex2rtf.  Tex2RTF really should be a separate project, but 
> I'm having a difficult time working on Jazz++ not alone Tex2RTF...
> 

....Uh-huh, and release pkgs are likewise...and of course,
the source tarball has everything except possibly tex2rtf,
(which is available separately), right? (this is me lobbying
my own position & requirements  ;-)


> DM> I'll guess yes...do we offer users a switch in release
> DM> form? I'm thinking --enable-tex2rtf builds and installs
> DM> tex2rtf system wide.
> 
> I think the last section of reply helps explain what I'm thinking.
> 
> DM> I'm in the state of Queensland or +10 (but take that
> DM> with a grain of salt, as I tend to keep rather peculiar
> DM> hours)
> 
> Understood.  Now I can pull up something like
> 
> http://www.worldtimezone.com/
> 
> and figure out how "fresh" you are ;-)
> 
> It's about 9:00 PM here now.
> 
> BTW, I can't thank you enough for all of the help!!!!!
> 

It's my pleasure, I'm glad you like my input...output..  ;-)


Regards,

Donald B
_________________________________________________________________
Are you paid what you're worth? Find out: SEEK Salary Centre
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT