Error in ./build.sh --skip-final-rsync iso about building-pfsense-iso-from-source HOT 6 CLOSED

Maybe I "solved" it with a little trick, that is by copying the symbolic link (in /usr/local/www/nginx/package) and then creating one with the version and one with the master. Practically
exoSphere_master_amd64-exoSphere_master -> /usr/local/poudriere/data/packages/exoSphere_v2_4_5_amd64-exoSphere_v2_4_5
exoSphere_v2_4_5_amd64-core -> /root/pfsense/tmp/exoSphere_v2_4_5_amd64-core/.latest
exoSphere_v2_4_5_amd64-exoSphere_v2_4_5 -> /usr/local/poudriere/data/packages/exoSphere_v2_4_5_amd64-exoSphere_v2_4_5

Even if there is some error but i try to use the iso. I keep you informed.
This was a work around, i'd like to understand the reason for a pure clear build!

thanks

Alessandro

from building-pfsense-iso-from-source.

The build, works, even if pfsense is written everywhere and only in some little place is exoSphere.. I think there is still a lot of works to do!

Thanks
Alessandro

from building-pfsense-iso-from-source.

Indeeed, it was a symbolic link issue ( I think you forgot to replace libresense by exosphere in your setup ? )

Can i close this issue now?

from building-pfsense-iso-from-source.

Yes it was a symbolic link issue but I'm sure enough I didn't forget to replace libraSense with exoSphere (to be 100% sure, in these days, i'll compile with libraSense directly, to avoid any change).
If you want you can close, in case i'll open a new one.
Another little hint i ask, can you suggest me, if you know, ho to change the brand directly in compilng phase? Witch file are direct involved?
Thanks a lot, you are very kind!
Alessandro

from building-pfsense-iso-from-source.

how to change the brand directly in compilng phase? Witch file are direct involved?

It's not that simple...there is references of pfsense everywhere in the code (from the boot logo to the files and functions names).

Some services(bug reporter, acb, etc...) have also some kind of interconnection with Netgate infra and therefore are specific to pfsense, there is no way to migrate them.

from building-pfsense-iso-from-source.

Sorry for "witch" it was a "Which" (as you correctly understood). :)
Yeah i understand. I don't wanna use other people code as mine, the pfsense and connection with netgate is due and all the credits are theirs. But i'd like to build a derivate like ubuntu from debian (where the world debian and the connection with the original linux os is not completly disappeared for common parts, sure not in the early versions ).
My goals is to build a my own version of pfsense, like opnsense for example, derivated from pfsense but with my brand and "security point of view" and for market porpose.
I'll investigate further.
If you want and there are not other useful tips for now, you can close this ticket.
In case i'll open another one.
Thank you for your preciuos support.
Your guide teached me a lot of things! Thanks very very much!
Alessandro

from building-pfsense-iso-from-source.