Closed
Bug 451909
Opened 16 years ago
Closed 16 years ago
kill MOZ_XUL_APP now that all apps set it
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.9.2a1
People
(Reporter: kairo, Assigned: Swatinem)
References
()
Details
Attachments
(12 files, 7 obsolete files)
534 bytes,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
505 bytes,
patch
|
dmosedale
:
review+
|
Details | Diff | Splinter Review |
2.12 KB,
patch
|
sdwilsh
:
review+
|
Details | Diff | Splinter Review |
639 bytes,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
4.02 KB,
patch
|
Bienvenu
:
review+
dbaron
:
superreview+
|
Details | Diff | Splinter Review |
5.97 KB,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
6.10 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
7.65 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
18.16 KB,
patch
|
Swatinem
:
review+
|
Details | Diff | Splinter Review |
643 bytes,
text/plain
|
Swatinem
:
review+
|
Details |
2.24 KB,
patch
|
Swatinem
:
review+
|
Details | Diff | Splinter Review |
2.19 KB,
patch
|
Swatinem
:
review+
|
Details | Diff | Splinter Review |
Now that we live on Mercurial, all apps building on our platform set MOZ_XUL_APP - Camino was the last app that didn't set it, but they are not on hg yet and should not migrate to 1.9.1 unless they finally convert to being based on toolkit. This means we can go for getting rid of code that is |ifndef MOZ_XUL_APP| and finally of the flag itself. As a first step, I'll probably do a patch that makes configure fail if the flag is not set so anything that might still build that way (I doubt it) is showing an error, then I'll remove |ifndef MOZ_XUL_APP| code step by step, removing the checks for the flag.
Reporter | ||
Comment 1•16 years ago
|
||
This patch makes us error out on builds that unset MOZ_XUL_APP in confvars.sh (can only happening there as nothing in our build system unsets it but configure sets it by default).
Attachment #335222 -
Flags: review?(ted.mielczarek)
Updated•16 years ago
|
Attachment #335222 -
Flags: review?(ted.mielczarek) → review+
Assignee | ||
Comment 2•16 years ago
|
||
KaiRo: If you don't mind I would like to take over this bug. I hope I understood it correctly that everything in code and makefiles that deals with MOZ_XUL_APP unset is to be removed, including complete directories like http://mxr.mozilla.org/comm-central/source/mozilla/embedding/browser/chrome/ ?
Reporter | ||
Comment 3•16 years ago
|
||
Right. Feel free to take over, I'll check in this first patch though. The URL I did set for this bug should actually point to all places that use MOZ_XUL_APP and all those places need changes. If we are only building a whole directy |ifndef MOZ_XUL_APP|, we should do a patch to remove all of it. Please do step-by-step patches though, they are easier to review than one large patch :)
Reporter | ||
Comment 4•16 years ago
|
||
Comment on attachment 335222 [details] [diff] [review] error out on builds unsetting MOZ_XUL_APP (checked in) OK, checked in this first patch. Now we can be really sure that everyone has the flag set and remove code that depends on it being unset (including the checks themselves).
Attachment #335222 -
Attachment description: error out on builds unsetting MOZ_XUL_APP → error out on builds unsetting MOZ_XUL_APP (checked in)
Assignee | ||
Comment 5•16 years ago
|
||
Assignee | ||
Updated•16 years ago
|
Attachment #335598 -
Flags: review? → review?(kairo)
Assignee | ||
Comment 6•16 years ago
|
||
I really don't know who I should ask for review here.
Assignee | ||
Comment 7•16 years ago
|
||
Attachment #335600 -
Flags: review?(benjamin)
Assignee | ||
Comment 8•16 years ago
|
||
Assignee | ||
Comment 9•16 years ago
|
||
Attachment #335602 -
Flags: review?(benjamin)
Assignee | ||
Comment 10•16 years ago
|
||
Attachment #335605 -
Flags: review?(neil)
Assignee | ||
Comment 11•16 years ago
|
||
Assignee | ||
Comment 12•16 years ago
|
||
Attachment #335607 -
Flags: review?(ted.mielczarek)
Assignee | ||
Comment 13•16 years ago
|
||
sorry, missed a few subdirs which can go away
Attachment #335607 -
Attachment is obsolete: true
Attachment #335610 -
Flags: review?(ted.mielczarek)
Attachment #335607 -
Flags: review?(ted.mielczarek)
Assignee | ||
Comment 14•16 years ago
|
||
This is a list of hg rm commands that removes directories or files which got obsolete due to makefile or jar.mn changes.
Assignee | ||
Comment 15•16 years ago
|
||
I'm sorry for yet another patch, forgot the makefiles in allmakefiles.sh. Whats still left to do: the configure.ins and autoconf.mk.ins of c-c and m-c. Also, I haven't touched the code of extensions/wallet and extensions/typeaheadfind, I don't want to mess around with cvs right now. I also found another problem in the list of hg removes: it's actually netwerk instead of network. If someone could please request review from the right reviewers, I'm not yet familiar with the reviewers of all those modules. Hope that was everything for now.
Attachment #335610 -
Attachment is obsolete: true
Attachment #335618 -
Flags: review?(ted.mielczarek)
Attachment #335610 -
Flags: review?(ted.mielczarek)
Updated•16 years ago
|
Attachment #335599 -
Flags: review?(sdwilsh)
Reporter | ||
Comment 16•16 years ago
|
||
Comment on attachment 335611 [details] list of hg removes >hg rm xpfe/components/startup >hg rm xpfe/components/xremote Those already have been removed.
Reporter | ||
Comment 17•16 years ago
|
||
Comment on attachment 335618 [details] [diff] [review] makefile cleanups (whole tree) v3 >diff -r 1d4a67cd6939 toolkit/toolkit-makefiles.sh >diff -r 1d4a67cd6939 toolkit/toolkit-tiers.mk >diff -r 1d4a67cd6939 xpfe/components/Makefile.in Those files were changed as well even before you did that patch. >diff -r 1d4a67cd6939 xpfe/components/winhooks/Makefile.in You might as well leave out winhooks completely, we are about to remove it completely once the new SeaMonkey shellservice UI lands.
Reporter | ||
Comment 18•16 years ago
|
||
Comment on attachment 335598 [details] [diff] [review] [checked in] mailnews cleanup I'm no mailnews owner or peer, forwarding to someone who actually can review there.
Attachment #335598 -
Flags: review?(kairo) → review?(dmose)
Comment 19•16 years ago
|
||
Comment on attachment 335599 [details] [diff] [review] [checked in] inspector cleanup r=sdwilsh
Attachment #335599 -
Flags: review?(sdwilsh) → review+
Assignee | ||
Comment 20•16 years ago
|
||
(In reply to comment #17) > (From update of attachment 335618 [details] [diff] [review]) > >diff -r 1d4a67cd6939 toolkit/toolkit-makefiles.sh > >diff -r 1d4a67cd6939 toolkit/toolkit-tiers.mk > >diff -r 1d4a67cd6939 xpfe/components/Makefile.in > > Those files were changed as well even before you did that patch. Yes, I noticed. Updated patch that applies fine after bug 380786 landed. I left winhooks in, shouldn't be that much of a problem I think.
Attachment #335618 -
Attachment is obsolete: true
Attachment #335815 -
Flags: review?(ted.mielczarek)
Attachment #335618 -
Flags: review?(ted.mielczarek)
Updated•16 years ago
|
Attachment #335600 -
Flags: review?(benjamin) → review+
Updated•16 years ago
|
Attachment #335602 -
Flags: review?(benjamin) → review+
Assignee | ||
Updated•16 years ago
|
Keywords: checkin-needed
Comment 21•16 years ago
|
||
Comment on attachment 335815 [details] [diff] [review] [checked in] makefile cleanups (whole tree) v4 diff -r 86a4475236c7 -r 90258f3e351f embedding/Makefile.in -ifndef MOZ_XUL_APP -DIRS += lite -endif You're just going to remove this dir, correct? diff -r 86a4475236c7 -r 90258f3e351f extensions/pref/autoconfig/Makefile.in -DIRS = public resources src +DIRS = public src Why did this directory become obsolete?
Attachment #335815 -
Flags: review?(ted.mielczarek) → review+
Assignee | ||
Comment 22•16 years ago
|
||
(In reply to comment #21) > (From update of attachment 335815 [details] [diff] [review]) > diff -r 86a4475236c7 -r 90258f3e351f embedding/Makefile.in > -ifndef MOZ_XUL_APP > -DIRS += lite > -endif > > You're just going to remove this dir, correct? Yes, it's listed in the hg removes file I attached. > diff -r 86a4475236c7 -r 90258f3e351f extensions/pref/autoconfig/Makefile.in > -DIRS = public resources src > +DIRS = public src > > Why did this directory become obsolete? The only thing in it is a jar.mn which is entirely #ifndef MOZ_XUL_APP, see http://mxr.mozilla.org/mozilla-central/source/extensions/pref/autoconfig/resources/jar.mn The same is true for some other dirs/jars. I think its better to completely remove them, they are listed in the removes attachment as well. Maybe you could review that removes file too? I didn't know who to ask for review there.
Updated•16 years ago
|
Attachment #335605 -
Flags: review?(neil) → review+
Comment 23•16 years ago
|
||
Comment on attachment 335605 [details] [diff] [review] xpfe cleanup > #include "nsComponentManagerUtils.h" > #include "nsServiceManagerUtils.h" > >-#ifdef MOZ_XUL_APP > #include "nsAppRunner.h" >-#endif You could get rid of that blank line too. r=me on nsContentTreeOwner.cpp (not shown here) and this file (both changes). >diff -r 15ca53e61c8d xpfe/browser/src/nsBrowserInstance.cpp I wouldn't bother touching nsBrowserInstance or nsWindowsHooks. As previously mentioned nsWindowsHooks will die shortly and if the code in nsBrowserInstance isn't going to be fixed to work with toolkit (which seems unlikely) then it and its callers should just be removed completely (although that probably deserves at least one new bug.)
Comment 24•16 years ago
|
||
Comment on attachment 335599 [details] [diff] [review] [checked in] inspector cleanup Checked into DOMI repository, changeset 658:bf67ee2f541e
Attachment #335599 -
Attachment description: inspector cleanup → [checked in] inspector cleanup
Comment 25•16 years ago
|
||
Comment on attachment 335600 [details] [diff] [review] [checked in] docshell cleanup docshell, toolkit and makefile cleanups checked in with changeset id: 18576:da4096b97530
Attachment #335600 -
Attachment description: docshell cleanup → [checked in] docshell cleanup
Updated•16 years ago
|
Attachment #335602 -
Attachment description: toolkit cleanup → [checked in] toolkit cleanup
Updated•16 years ago
|
Attachment #335815 -
Attachment description: makefile cleanups (whole tree) v4 → [checked in] makefile cleanups (whole tree) v4
Comment 26•16 years ago
|
||
I think I've checked in what I can here: - xpfe patch needs update before checkin - extensions cleanup needs review - jar.mn cleanup needs review (ted possibly?) - hg removes need review (again ted?) - mailnews patch is awaiting review.
Keywords: checkin-needed
Updated•16 years ago
|
Attachment #335611 -
Flags: review+
Updated•16 years ago
|
Attachment #335598 -
Flags: review?(dmose) → review+
Comment 27•16 years ago
|
||
Comment on attachment 335598 [details] [diff] [review] [checked in] mailnews cleanup r=dmose
Comment 28•16 years ago
|
||
Comment on attachment 335598 [details] [diff] [review] [checked in] mailnews cleanup Checked in, changeset id: 257:9cc1aca930cc
Attachment #335598 -
Attachment description: mailnews cleanup → [checked in] mailnews cleanup
Assignee | ||
Comment 29•16 years ago
|
||
(In reply to comment #23) > (From update of attachment 335605 [details] [diff] [review]) > You could get rid of that blank line too. r=me on nsContentTreeOwner.cpp (not > shown here) and this file (both changes). done > I wouldn't bother touching nsBrowserInstance or nsWindowsHooks. As previously > mentioned nsWindowsHooks will die shortly and if the code in nsBrowserInstance > isn't going to be fixed to work with toolkit (which seems unlikely) then it and > its callers should just be removed completely (although that probably deserves > at least one new bug.) Winhooks was removed, right. This patch is updated to apply cleanly after those changes. It was easier for me to just leave the BrowserInstance changes in. It should be dealt with in another bug I believe. Apart from this, the patch is unchanged so I believe it doesn't need another review.
Attachment #335605 -
Attachment is obsolete: true
Assignee | ||
Comment 30•16 years ago
|
||
removed the already removed directories and fixed the netwerk typo.
Attachment #335611 -
Attachment is obsolete: true
Reporter | ||
Comment 31•16 years ago
|
||
(In reply to comment #29) > Apart from this, the patch is unchanged so I believe it doesn't need another > review. Then you should mark the review+, i.e. "forward" it to the new patch. Also, you should set the checkin-needed keyword so people know something here needs to be checked in. Oh, and does the jar.mn patch have review yet?
Assignee | ||
Updated•16 years ago
|
Attachment #337740 -
Flags: review+
Assignee | ||
Updated•16 years ago
|
Attachment #337745 -
Attachment mime type: application/octet-stream → text/plain
Attachment #337745 -
Flags: review+
Assignee | ||
Updated•16 years ago
|
Attachment #335606 -
Flags: review?(ted.mielczarek)
Assignee | ||
Comment 32•16 years ago
|
||
Well, ok then, the xpfe patch should be ready. The hg removes should only be checked in after the jars patch got review and check-in.
Keywords: checkin-needed
Updated•16 years ago
|
Attachment #335606 -
Flags: review?(ted.mielczarek) → review+
Comment 33•16 years ago
|
||
Comment on attachment 337740 [details] [diff] [review] updated xpfe cleanup [Checkin: Comment 33] http://hg.mozilla.org/mozilla-central/rev/d5e4a3e10202
Attachment #337740 -
Attachment description: updated xpfe cleanup → updated xpfe cleanup
[Checkin: Comment 33]
Comment 34•16 years ago
|
||
Comment on attachment 335606 [details] [diff] [review] jar.mn cleanup (whole tree) [Checkin: Comment 34] http://hg.mozilla.org/mozilla-central/rev/9b921a3fdb5e
Attachment #335606 -
Attachment description: jar.mn cleanup (whole tree) → jar.mn cleanup (whole tree)
[Checkin: Comment 34]
Comment 35•16 years ago
|
||
Arpad, in cases like this, please add a whiteboard note to be explicit about which patch(s) to check in; also, when you forward a '+', you may copy/remind in the comment who you are forwarding from. Thanks.
Comment 36•16 years ago
|
||
Comment on attachment 337745 [details] updated removes file [Checkin: Comment 36] http://hg.mozilla.org/mozilla-central/rev/f0f5edda2633 NB: Hg commands are (probably) fine for review, but please attach a patch for (easier) checkin.
Attachment #337745 -
Attachment description: updated removes file → updated removes file
[Checkin: Comment 36]
Updated•16 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Flags: in-testsuite-
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.1b1
Comment 37•16 years ago
|
||
Reopening: doesn't seem fully fixed yet :-/
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 38•16 years ago
|
||
Yes, the extensions patch (spellchecker, layout-debug) still needs review but I have no idea who should be reviewing that. And I will do the complete removal of that flag from configure once its users are all gone from the tree. I'm not sure yet if I should completely remove it or leave the warning in and just set it to be always defined.
Reporter | ||
Comment 39•16 years ago
|
||
(In reply to comment #38) > I'm not sure yet if I should completely remove it or leave the warning in and > just set it to be always defined. IMHO, we should completely remove it - from both mozilla-central and comm-central.
Comment 40•16 years ago
|
||
dbaron can review layout-debug. I'm not sure who would review spellchecker.
Reporter | ||
Comment 41•16 years ago
|
||
spellchecker is currently pretty much un-owned, we are looking to find a solution but have none yet. It's probably best to look for people who did review or change code in that module somewhat recently (except mscott, who is pretty much unavailable).
Comment 43•16 years ago
|
||
Comment on attachment 335601 [details] [diff] [review] extensions cleanup (spellchecker, layout-debug) [Checkin: Comment 49] Asking dbaron for layout-debug and smorgan for spellcheck.
Attachment #335601 -
Flags: superreview?(dbaron)
Attachment #335601 -
Flags: review?(stuart.morgan+bugzilla)
Comment 44•16 years ago
|
||
Comment on attachment 335601 [details] [diff] [review] extensions cleanup (spellchecker, layout-debug) [Checkin: Comment 49] I have nothing to do with spellcheck.
Attachment #335601 -
Flags: review?(stuart.morgan+bugzilla)
Comment on attachment 335601 [details] [diff] [review] extensions cleanup (spellchecker, layout-debug) [Checkin: Comment 49] sr=dbaron
Attachment #335601 -
Flags: superreview?(dbaron) → superreview+
Comment 46•16 years ago
|
||
Comment on attachment 335601 [details] [diff] [review] extensions cleanup (spellchecker, layout-debug) [Checkin: Comment 49] bienvenu, can you review a little dead code removal (MOZ_XUL_APP ifdefs) in spellcheck, please?
Attachment #335601 -
Flags: review?(bienvenu)
Comment 47•16 years ago
|
||
Comment on attachment 335601 [details] [diff] [review] extensions cleanup (spellchecker, layout-debug) [Checkin: Comment 49] r= me for spellcheck - layout debug is not something I'm remotely involved with, but you could switch dbaron's sr to an r= and sr=me for that - it looks fine.
Attachment #335601 -
Flags: review?(bienvenu) → review+
Assignee | ||
Comment 48•16 years ago
|
||
Adding checkin-needed with review flags according to comment #47. extensions/(wallet|typeaheadfind) are still using the macro, so I can't completely remove the macro from configure yet :(
Keywords: checkin-needed
Whiteboard: [checkin with flags according to comment 47]
Comment 49•16 years ago
|
||
Comment on attachment 335601 [details] [diff] [review] extensions cleanup (spellchecker, layout-debug) [Checkin: Comment 49] http://hg.mozilla.org/mozilla-central/rev/f9f55538ed8c
Attachment #335601 -
Attachment description: extensions cleanup (spellchecker, layout-debug) → extensions cleanup (spellchecker, layout-debug)
[Checkin: Comment 49]
Updated•16 years ago
|
Severity: normal → trivial
Status: REOPENED → ASSIGNED
Keywords: checkin-needed
Whiteboard: [checkin with flags according to comment 47]
Target Milestone: mozilla1.9.1b1 → mozilla1.9.1b2
Reporter | ||
Comment 50•16 years ago
|
||
(In reply to comment #48) > extensions/(wallet|typeaheadfind) are still using the macro, so I can't > completely remove the macro from configure yet :( Both should die/move in the next months (the former will, I hope we can do that for the latter as well in some way), I think we can leave the existence of the flag in for that atm.
Assignee | ||
Comment 51•16 years ago
|
||
(In reply to comment #50) > Both should die/move in the next months Is the progress tracked in a bug? Can you make it block this one?
Assignee | ||
Comment 52•16 years ago
|
||
Attachment #344822 -
Flags: review?(ted.mielczarek)
Assignee | ||
Comment 53•16 years ago
|
||
Ted: you are also responsible for the c-c build system, right? The patches are not yet meant for checkin, as long as extensions/(wallet|typeaheadfind) aren't dealt with first. See comment #50.
Attachment #344823 -
Flags: review?(ted.mielczarek)
Comment 54•16 years ago
|
||
I don't own the c-c build system. You can ask Kairo or Standard8 for review.
Comment 55•16 years ago
|
||
Comment on attachment 344822 [details] [diff] [review] configure cleanup, mozilla-central +MOZ_PROFILESHARING= What's this change for? Looks fine otherwise.
Attachment #344822 -
Flags: review?(ted.mielczarek) → review+
Comment 56•16 years ago
|
||
Comment on attachment 344823 [details] [diff] [review] configure cleanup, comm-central I am also a c-c build peer, I just focus on client.py :-) c#55 intrigues me as well... Also, we (c-c) can't remove MOZ_XUL_APP just yet, [see: http://mxr.mozilla.org/comm-central/search?find=%2Fmozilla%2Fextensions%2F&string=MOZ_XUL_APP] Both those dirs are currently pulled from CVS via client.py and a solution needs to be found for them first. (I'm not sure top of my head if camino uses them or not).
Attachment #344823 -
Flags: review?(ted.mielczarek) → review-
Comment 57•16 years ago
|
||
actually, re: m-c and c-c final removals, I believe that removing MOZ_XUL_APP from m-c's autoconf.mk will break those, and c-c's autoconf.mk likely won't matter... KaiRo, have any ideas I'm overlooking?
Assignee | ||
Comment 58•16 years ago
|
||
(In reply to comment #55) > +MOZ_PROFILESHARING= > > What's this change for? Looks fine otherwise. Thats what the old code did. The code in question was added by bug 261232, so I'm CC-ing Benjamin who did that change. Maybe he can shed more light on that. (In reply to comment #56) > Also, we (c-c) can't remove MOZ_XUL_APP just yet I'm well aware of that. Thats why I said that these patches are not yet meant for checkin before those extensions aren't cleaned up first.
Comment 59•16 years ago
|
||
Comment on attachment 344823 [details] [diff] [review] configure cleanup, comm-central r+ re: c#58 then, thanks
Attachment #344823 -
Flags: review- → review+
Reporter | ||
Comment 60•16 years ago
|
||
Just as a note, Justin is right, we probably can even remove the flag from c-c completely but we actually need to keep it in m-c for those modules in extensions/ directories as they are built with the m-c build system.
Assignee | ||
Updated•16 years ago
|
Whiteboard: [do not check in latest patches]
Assignee | ||
Updated•16 years ago
|
Comment 61•16 years ago
|
||
Wallet is now "gone" - we're not building it any more (though currently we are still pulling it).
Assignee | ||
Comment 62•16 years ago
|
||
(In reply to comment #61) > Wallet is now "gone" - we're not building it any more (though currently we are > still pulling it). Good job, requesting checkin-needed for the last 2 patches then.
Keywords: checkin-needed
Whiteboard: [do not check in latest patches] → [checkin configure cleanup]
Both patches need refreshing, they don't apply cleanly.
Assignee | ||
Comment 64•16 years ago
|
||
Attachment #344822 -
Attachment is obsolete: true
Attachment #357632 -
Flags: review+
Assignee | ||
Comment 65•16 years ago
|
||
Both patches refreshed, carrying over r+
Attachment #344823 -
Attachment is obsolete: true
Attachment #357633 -
Flags: review+
Comment 66•16 years ago
|
||
Comment on attachment 357632 [details] [diff] [review] configure cleanup, mozilla-central, refreshed [Checkin: Comment 66] http://hg.mozilla.org/mozilla-central/rev/cc99d1111d78
Attachment #357632 -
Attachment description: configure cleanup, mozilla-central, refreshed → configure cleanup, mozilla-central, refreshed
[Checkin: Comment 66]
Comment 67•16 years ago
|
||
Comment on attachment 357633 [details] [diff] [review] configure cleanup, comm-central, refreshed [Checkin: Comment 67] http://hg.mozilla.org/comm-central/rev/31bb673606da
Attachment #357633 -
Attachment description: configure cleanup, comm-central, refreshed → configure cleanup, comm-central, refreshed
[Checkin: Comment 67]
Updated•16 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 16 years ago → 16 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Whiteboard: [checkin configure cleanup]
Target Milestone: mozilla1.9.1b2 → mozilla1.9.2a1
Comment 68•16 years ago
|
||
(In reply to comment #67) It seems one file remains to be processed: http://mxr.mozilla.org/comm-central/search?string=MOZ_XUL_APP&case=on&find=%2Fsuite%2Finstaller%2Fwindows%2Fpackages
Assignee | ||
Comment 69•16 years ago
|
||
Those are just comments saying when each of those packaged files was added, I left that comment in intentionally. So yes, this is fixed now, thanks everyone for review & checkin :)
Updated•6 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•