Re: Profile support in apt
On 30 January 2013 01:37, Johannes Schauer <j.schauer@email.de> wrote:
> So what would be the preferred way to read the variable in the frontend
> and pass it to the backend? A new global variable? Or store it as part
> of _config? In that case a configuration variable APT::Profile could be
> introduced, symmetric to APT::Architecture. But then again: no other
> configuration currently has the option to be given by an environment
> variable. Also, a profile is always selected on a per-package basis and
> will never (and should never) be set globally.
Another option is to extend BuildDepRec (apt-pkg/srcrecords.h) to
contain a list of profiles. Frontends — particularly interactive ones
— are then aware of the full information, and can present some
interface to users. Also, the filtering logic (which should certainly
be in libapt, rather than a particular frontend) could then be
separated from ParseDepends and optional, if convenient. Handling
architectures in this way would also be useful.
Regards
Reply to: