Re: library.ecf for not void safe

--===============5930090570555967139==
Content-Type: multipart/signed;
	boundary="pgp-sign-Multipart_Thu_May_26_09:35:09_2016-1";
	micalg=pgp-sha256; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit

--pgp-sign-Multipart_Thu_May_26_09:35:09_2016-1
Content-Type: text/plain; format=flowed; charset=US-ASCII

>>>>> "Eric" == Eric Bezault <[email protected]> writes:

    Eric> The reason why I put only one ECF file is that I don't want
    Eric> to have to maintain several ECF files. That's why we
    Eric> invented Xace in the first place: avoid having to maintain
    Eric> multiple files.

It seems your current .ecf files were hand-generated, so that's why I
mentioned this.

But isn't this only temporary? I.e. once we all move to void safe, I
think ecf is sufficient, isn't it?


So another solution would be a gexace patch then. Just changing the
version number solves most of the problems. It seems ISE Eiffel is
extremely finicky on having the same versions on all .ecf files,
mixing versions produces very odd results.


But does generating library ecf files work actually? I noticed you
have to repeat include a reference to every library that is used by a
library, so a completely different concept from xace.


But having gexace generate a single .ecf file with a single ecf
version number for a system sounds like a much simpler world than what
ecf is currently trying to achieve.

--
All the best,

Berend de Boer


--pgp-sign-Multipart_Thu_May_26_09:35:09_2016-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
Content-Description: OpenPGP Digital Signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAABCAAGBQJXRhqNAAoJEKOfeD48G3g5o+YQAKEqC3fguaHnbkabZj5hwyPW
O/v3nUSNE+sLr0cC4Zbno06mKz9qytxZD92uA+pVU8hAud2ex8sZhoGY+sLlmncY
pC5h5tT1Ho2UtB6bJaTQvFlzUQ6weWLmZMGqzVWQg4p2C2xECByOw4un5A0aZRXa
nFkCXQ8+wEumRwO01A7Hrz+yeTwOHyZks/zsAv+VSjoylX6DZEGL1txFqaP1kQu9
XifO+gv+3Sg1065O7M8wZ6N5wxLq3n82ngk6v5jjwriDL3bwlUYA3dckgCL5EMyz
r0BrmcYcQ2mT7qWL1g2wHPd9qsgtd7PqpNGHkfp2J39d0ICR7Vqj9GWXhZWsslni
UdlnoMnUuhD2awuQyXcyh1pk+RbCRC/sZm9LFJUYTry3QcsMHFDY6DnKWTwqv4pj
/W5lWOMc7v0BmRo21Q43o39juj0fLcXs1NU57/MfTI9RoSAdl4bo57pldr2eub3v
waEXQ4nTyBYTVV6vWRKz+837qNEhjGyjk5XxCk1nPiBikDkWCbBIetJt0zwnts9T
MvdMxUGloij+Ee+o2KEZPbb1M+ET2uzExBR9FZlVoFLf+AXMLUq/DjiriIFtSwto
iV2CrGB9BK9ihEpL8fPdA4BPLdNT8hfOZ6OpIDAGB8UTmCDr19VQ9jkiFPUKTUCE
160iVlgosdNfBk65VlRl
=1bWO
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Thu_May_26_09:35:09_2016-1--


--===============5930090570555967139==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
--===============5930090570555967139==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
gobo-eiffel-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop

--===============5930090570555967139==--