[PkgInfo} Munki2 What's new/changelog description key

[GoogleCodeExporter]

Perhaps we should add a second description key

Our current description key in pkginfo is great, but as Munki2 descriptions 
will look better with HTML, perhaps we should add a second set.

On MAS, there is a general description of the product/feature set and then a 
What's New section that shows a brief changelog.

munkiimport/pkginfo could then pull the current description over when an 
updated app is imported, but the admin could append this second description key 
with what's new.

Original issue reported on code.google.com by eriknico...@gmail.com on 23 Mar 2014 at 2:51

Attachments:

• [Screen Shot 2014-03-22 at 9.50.51 PM.png](https://storage.googleapis.com/google-code-attachments/munki/issue-297/comment-0/Screen Shot 2014-03-22 at 9.50.51 PM.png)

[GoogleCodeExporter]

I considered this, but rejected it. I don't think many admins are going to be 
religiously updating descriptions; they'll write a description once and let 
munkiimport bring it forward for new releases, or they'll use a tool like 
AutoPkg to automate things.

There's nothing stopping an admin from adding a "What's new" to the existing 
description field.

(There's also nothing stopping a pkginfo creation tool from asking for a 
"What's New" section and adding it to the existing description field.

pkginfo files already have a bewildering array of possible keys; I'd love to 
find ways to get rid of some! This doesn't seem worthy of adding yet another.

Original comment by gregnea...@mac.com on 23 Mar 2014 at 2:57

• Changed state: WontFix

[GoogleCodeExporter]

Could you possibly change the base.css file to add h1 functionality then?

As it stands, the admin can add a What's new section, but it's still a set font 
size, based off h4.

Original comment by eriknico...@gmail.com on 23 Mar 2014 at 4:06

Attachments:

• [Apple Configurator-1.5.plist](https://storage.googleapis.com/google-code-attachments/munki/issue-297/comment-2/Apple Configurator-1.5.plist)

[GoogleCodeExporter]

Or rather h2.

Original comment by eriknico...@gmail.com on 23 Mar 2014 at 4:08

[GoogleCodeExporter]

This is difficult.

The HTML description has to be transformed to remove all block-level elements 
and replace them with inline elements. This is because the description must fit 
into a paragraph element.

See: 
https://code.google.com/p/munki/source/browse/code/Managed%20Software%20Center/M
anaged%20Software%20Center/msulib.py?name=Munki2#38

It might be possible in the future to address this, but is not terribly high on 
my priority list at this time.

Original comment by gregnea...@mac.com on 23 Mar 2014 at 7:34

[GoogleCodeExporter]

Okay no problem. Interesting stuff in that file. I wish I had looked through 
that last night when I was playing with these description's.

Original comment by eriknico...@gmail.com on 23 Mar 2014 at 8:48