Hi John,
there is one issue which prevents us from doing what you described:
we're modifying some .c files in libraries, so you can't just copy them
from upstream repository, you'll need to modify them before building.
Other than that quite often updated library version is not fully 100%
backward compatible, so we usually fixing that issues too.
> Yes, it would make the virtualbox archive not self-sufficient,
but then it is already not self-sufficient.
It should be, if not - that's an issue which has to be fixed.
> Also maybe a friendly request to the curl upstream maintainer asking
for whatever is needed to be exposed in an installed curl, so that
package source files would not be needed at all.
Please don't forget we're building VirtualBox not for Linux only, we
build it for Windows, for example, where that solution would hardly work.
On 01/05/2023 18:35, John Lumby via vbox-dev wrote:
Referencing the previous posts on this from Konstantin Vlasov and the issuing of the new
suffix-"a" archives :
I also just got hit by this (missed the significance of the earlier posts,
duh!)
But surely packaging another package's source includes and even c-files is not
a good idea - this problem is bound to happen again.
I would suggest, instead, adding a new mandatory parameter to configure
---curl-source-tree=/somewhere
with an explanation of how to obtain this source-tree (or even automatically
git-clone it if missing?)
and adding that directory to the g++ include list
Yes, it would make the virtualbox archive not self-sufficient, but then
it is already not self-sufficient.
Also maybe a friendly request to the curl upstream maintainer asking for
whatever is needed to be exposed in an installed curl, so that package source
files would not be needed at all.
Cheers, John Lumby
_______________________________________________
vbox-dev mailing list
vbox-dev@virtualbox.org
https://www.virtualbox.org/mailman/listinfo/vbox-dev
_______________________________________________
vbox-dev mailing list
vbox-dev@virtualbox.org
https://www.virtualbox.org/mailman/listinfo/vbox-dev
