Issue 779 - Need new 'product' for configure / build related bugs
Summary: Need new 'product' for configure / build related bugs
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Bugzilla (show other issues)
Version: current
Hardware: PC Other OS
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-04-25 23:28 UTC by zeroj
Modified: 2007-10-13 09:33 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
xml2cmp/source/xcd/parse.cxx : Workaround (667 bytes, patch)
2001-04-26 08:58 UTC, zeroj
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description zeroj 2001-04-25 23:28:25 UTC
There is no clear 'product' against which to file bugs relating to the build 
system.

Two products which sound related are utilities & tools.  If either of these is 
in fact build related, could the description be changed to indicate that.

utilities: This is the project for utilities used in development. 
tools: These are the tools used in the build process and the build environment.
Comment 1 Unknown 2001-04-25 23:38:59 UTC
what do you mean by "bugs relating to the build system"?  Do you mean bugs 
encountered during the build process?  Or bugs with the build processs itself?

Either way, it's the dev@tools.openoffice.org list you want.

I'll try and add a clarification word or two in the project description, how 
about:

"All issues relating to the build process and the build environment."
Comment 2 Unknown 2001-04-25 23:44:50 UTC
Taking issue
Comment 3 Unknown 2001-04-25 23:45:22 UTC
really taking issue >;-)
Comment 4 zeroj 2001-04-25 23:47:21 UTC
I mean I have a patch to configure.in , and I want to raise a bug ... and 
attach a patch.  Actually I have lots of these ... as I am working on the IRIX 
port.  Some are build related (config_office) , others are in 
xml2cmp,external,sal,vos,store,tools,inet & transex3
Comment 5 Unknown 2001-04-26 00:09:57 UTC
OK, I understand.

We obviously havn't gotten to the point of documenting most of this stuff.  I 
think the easiest way for you to do this is going to be to join the porting 
project dev list (dev-subscribe@porting.openoffice.org) and post there about 
your current status (you have patches to submit and how should you go about 
doing it).  Sander, Kevin, and others in the porting crew are very responsive 
and helpfull about this, esp. if you have patches.


Comment 6 zeroj 2001-04-26 00:15:34 UTC
I have an Issue / Bug and I wish to report it, and offer a fix it to.  Is this 
not the right system for this?  I am also the maintianer of the IRIX port of 
Mozilla, and if mailing lists are used in preference to issuezilla, then Open 
Office has learnt nothing from Mozilla.
What is IssueZilla used for then ?  
Comment 7 zeroj 2001-04-26 04:30:21 UTC
Please note that given I was directed to ask this question to dev@, and 
recieved no reply, I have chosen to file all bugs against tools, as this 
product mentions the word 'build' twice (very technical reasoning), as Sander 
has planned to put the IRIX patches into 627B and I am in .au, hence wont be 
working when he starts tomorrow.  Please feel free to move then around as fit.
Comment 8 zeroj 2001-04-26 08:58:22 UTC
Created attachment 170 [details]
xml2cmp/source/xcd/parse.cxx : Workaround
Comment 9 zeroj 2001-04-26 09:00:05 UTC
Ack ... that patch is for the wrong bug.  Apologies.
Comment 10 Unknown 2001-06-14 01:07:12 UTC
John, 

Has this issue been resolved?  There's been no activity in a number of weeks... 
did you get any help on the lists?
Comment 11 zeroj 2001-06-14 02:29:31 UTC
I was informed I should use 'porting' for my build related issues, so this bug 
can be closed.
Comment 12 lsuarezpotts 2001-07-10 17:21:09 UTC
closing issue per developer request
Comment 13 Raphael Bircher 2007-10-13 09:33:02 UTC
close now