| 1 |
On Tue, 8 Feb 2011, Fabian Groffen wrote: |
| 2 |
|
| 3 |
> On 08-02-2011 21:43:46 +0300, Konstantin Tokarev wrote: |
| 4 |
>> 08.02.2011, 09:21, mattmatteh@×××××.com: |
| 5 |
>>> perhaps a use flag bundle would be need. ideally your app should work both ways. |
| 6 |
>> |
| 7 |
>> I can imagine global setting of "CONFIG -= app_bundle" for all |
| 8 |
>> qmake-base ebuilds as implementation of USE="-bundles", but I'm not |
| 9 |
>> sure that all applications will be able to find their resources or |
| 10 |
>> plugins after this trick |
| 11 |
> |
| 12 |
> I'm not in favour of adding a USE-flag for bundle installs. I think we |
| 13 |
> should try to fix up the eclass, such that it installs perhaps symlinks |
| 14 |
> pointing to the bundle versions. |
| 15 |
|
| 16 |
not sure i am either. some applications support the unix install, and |
| 17 |
some support a bundle install, some support both ? so how can we support |
| 18 |
each of those installs ? |
| 19 |
|
| 20 |
also, if a package defaults to a bundle install, doesnt that usually have |
| 21 |
all the dependency libs packaged too ? |
| 22 |
|
| 23 |
if prefix were to make the bundle app in ${EPREFIX}/Applications would |
| 24 |
that be symlinks to ${EPREFIX}/path/to/file ? |
Archives