I had missed this aspect of your use case. The category approach previously mentioned will somewhat provide "one entry" to select for the user but there will still be a case where the user can drill down and unselect things.
On 2010-12-22, at 10:15 AM, Jacek Pospychała wrote: > does this allow for further independent modifications of refered features? > Afaik, trying to remove or update one of them will lead to dependency errors > from the main feature. > > > On Wed, Dec 22, 2010 at 3:55 PM, Pascal Rapicault <[email protected]> wrote: > Simply create a feature that refers to these two features and you are set. > > On 2010-12-22, at 6:14 AM, Pradeep Fernando wrote: > > > hi , > > > > Can we group two or more features together, so that instead of > > installing several features from a p2-repo, user can install only one > > feature. > > The problem is that the grouped features are not depending on each > > other:- they should be able to managed independently using p2-API > > after the installation. > > > > just that we have to provide a better abstraction to the user. > > > > thanks in advance. > > -- > > Pradeep Fernando. > > _______________________________________________ > > p2-dev mailing list > > [email protected] > > https://dev.eclipse.org/mailman/listinfo/p2-dev > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
