mardor/mozilla.py <- what's the intent?

mozilla-releng / build-mar

Utility for managing mar files

Mozilla Public License 2.0

8 stars 13 forks source link

mardor/mozilla.py <- what's the intent? #41

Closed hwine closed 6 years ago

hwine commented 6 years ago

Currently, it has both the primary & secondary keys that are currently active for release.

Is the intent to keep it in sync with changes?

Are you open to also adding some history and metadata? (active dates)

THANK YOU for this package!

catlee commented 6 years ago

I would like to keep them in sync with changes. The get_mozilla_keys.sh script will suck down the latest supported keys.

I haven't thought about how to handle historic keys and metadata. Do you have any ideas?

hwine commented 6 years ago

I probably will have ideas, but not yet. :) I mostly asked now to know whether or not I had to fork.

For now, I'll assume I'll use a separate file for historic keys. That will keep your build process intact.

The "history" support is more of a "nice to have" feature on my end. Even the exe handling doesn't support ancient history (unsigned stub installers).