Track request(classic) for the tree snap


#1

Dear @reviewers, I would like to request the classic track for the tree snap. This track is meant to provide an alternative distribution of the tree command that is in classic confinement while shipping the strictly confined ones in the latest track simultaneously.

The classic confinement usage is being discussed in [revoked] Classic confinement request for the tree snap .


Thanks in advance!


[revoked] Classic confinement request for the tree snap
Who to contact on package (tree) with no valid owner?
#2

Bumping topic…

Just try to tree /snap/pre-commit/current and it reminds me of this topic :slight_smile:


#3

Hello,

Sorry! At this point, we’re in “extension” territory since we didn’t get enough votes in the first 7 days of voting. @reviewers, could you please have a look and cast votes/opinions on this request? We’ll check for any votes or results on April 29th.

This is similar to New track(classic) request for the nano snap (which is also awaiting resolution). The version of the software being shipped in latest and classic is generally the same, which is not what tracks were envisioned for.

As for nano, classic has to be granted for the snap anyway (i.e. granting the track doesn’t negate the need to approve classic confinement for the snap which would be used on some revisions and not others) - I’m not sure I see much point on having the non-classic version available as well, as the usability will be much reduced (about the only use case I see is install-ability on Ubuntu Core systems, IMO much less of an issue with tree than it is with nano).

Consistent with my thoughts on nano, my particular vote is -1 out of being strict on track semantics and purpose (though I’m hoping other reviewers can chime in and we can suggest a good alternative for this use case).

  • Daniel