Problem - 2 - common packages
I have considered having a /packages/wayland/$packagename setup as it
seems how T2 does it now, except.....
In a number of cases I need to build the same package with more than one
configuration.
Such as having for a particular $package :
For its wayland build it will need --disablex-org --enablewayland in the
configuration file to build to run on a wayland server;
but;
For its X-org build it will need --disablewayland --enablex-org in the
configuration file to build to run on a x-org server!
etc.
BUT it's the same package, same version, and has the same name AT THIS
POINT, even though when installed, it will reside in a different
directory! Thank goodness!
Is there a current way to handle this in T2 as both need building and
naming differently at some point (where ?/? how please) to separate them
until installed.
Or is there a way to handle this in the one
/package/????/$packagename/$packagename.conf file? That would make it
easier on everyone in the long run I think.
At the moment there seems to be about 20 of them, but we know how the
list seems to grow when developing, don't we.
regards
jon
(and i haven't got to the hardest ones yet, but I want to have a good go
at understanding them before I yell for help)
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
