[Bug 833053] Re: license_key_path should not (yet) support per-user location

[Michael Nelson]

Hi Sebastian. I believe achuni and mvo agreed about copying the
license_key_path value into the package, but I'm not sure when that will
happen (and haven't yet seen a separate bug for it).

Regarding the validation we should include in the UI (it's just helping
devs identify early values that they won't be able to use for
license_key_path), you mention /opt/pkgname/conf.d - can you list all
items we should not allow through validation? (and wouldn't the license
key be written as a file without executable perms?)

And yes, currently we're catering only for one license key per install
(but eventually per user also - I assume).

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to aptdaemon in Ubuntu.
https://bugs.launchpad.net/bugs/833053

Title:
  license_key_path should not (yet) support per-user location

Status in Online service used by software center:
  New
Status in “aptdaemon” package in Ubuntu:
  New

Bug description:
  Currently USC won't allow a second user on a single system to purchase
  an app that is already installed, so we need to ensure that the
  devportal doesn't (yet) allow license_key_path using the home
  directory.

  That said, while I was JDIing that, the current implementation allows
  a license file directly in /opt which seems sub-optimal (ie. potential
  conflicts with other files). After chatting with Anthony, we thought
  that for a system-wide license_key_path, it should be a relative
  pathname - relative to the executable location (ie. within
  /opt/[package_name]/).

To manage notifications about this bug go to:
https://bugs.launchpad.net/software-center-agent/+bug/833053/+subscriptions