226942 - creating a distribution package does not add calendar

Status: RESOLVED WONTFIX

(SeaMonkey :: Build Config, defect)

Description

[Matus UHLAR - fantomas]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031127
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031127

when "building mozilla distribution" via

cd xpinstall/packager
make dist MOZ_PKG_DEST=...

the calendar is not added to the dirtribution, even if I requested building of
it by using --enable-calendar configure option. I think that if a user asks for
calendar, it should be added into the package too.

Reproducible: Always

Steps to Reproduce:
1. configure mozilla with calendar enabled
2. create mozilla tarball
3. unzip the tarrball  to destination directory

Actual Results:  
the calendar is not included

Expected Results:  
if user wishes to build a calendar, the calendar files should be added to the
tarball.

Comment 1

[Mostafa Hosseini]

packages-unix needs these lines:

[calendar]
bin/components/libxpical.so
bin/components/calendar.xpt
bin/chrome/calendar.jar

and packages-win needs these:
[calendar]
bin/components/xpical.dll
bin/components/calendar.xpt
bin/chrome/calendar.jar

other os's need similar lines.

Comment 2

[Benjamin Smedberg]

Do you need this for 1.6? My new packaging system landing when 1.7a opens will
make this problem mostly obsolete.

--BDS

Comment 3

[Matus UHLAR - fantomas]

That can wait, however I hope it will be launched soon.

Comment 4

[Vaclav Dvorak]

(In reply to comment #2)
> Do you need this for 1.6? My new packaging system landing when 1.7a opens will
> make this problem mostly obsolete.

What's the status on the new packaging system? Is there a bug that tracks it? Is
there any documentation somewhere? Thanks.

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Robert Kaiser]

I don't see any useful stuff in this bug for SeaMonkey specifically. Please
file new bugs in the correct places if there are still issues.