Ubuntu ppa - How is it made?
Is it built from sources? How does it solve the 32-bit lib problem? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Ubuntu-ppa-How-is-it-made-tp4819663.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Am 15.04.2015 um 13:28 schrieb Sean P. DeNigris <sean@clipperadams.com>:
Is it built from sources? How does it solve the 32-bit lib problem?
Yes it is built from sources. In the older distributions there were explicit 32bit packages, e.g. the infamous ia32-libs. Later they introduced architectures in the mix, so you can add a package:i386 to select the i386 version of it. Taking this it is just a matter of putting the right dependencies in the package file. Norbert
NorbertHartl wrote
Taking this it is just a matter of putting the right dependencies in the package file.
Is our process documented somewhere? Could it be automated e.g. by our CI? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Ubuntu-ppa-How-is-it-made-tp4819663p4819712.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Sean, Damien Cassou originally created the scripts I am using. There are a few manual steps involved that can be IMO automated. Look at https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-vm-core-i386 https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-launcher https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-vm Best regards, Markus On 15.04.2015 17:15, Sean P. DeNigris wrote:
NorbertHartl wrote
Taking this it is just a matter of putting the right dependencies in the package file.
Is our process documented somewhere? Could it be automated e.g. by our CI?
----- Cheers, Sean -- View this message in context: http://forum.world.st/Ubuntu-ppa-How-is-it-made-tp4819663p4819712.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQFcBAEBAgAGBQJVLpp3AAoJEDhtnsHwg7Ep+dUJ/jJHQkBvcSGA0TkfypuuCaDc iQmFMkq1NfxTGejFr0jQPAZVeX5igIC5gX0Rfqf8v4iAPmynzClAX/bPmasI9Jwv jWhjNfmGNK+/KDuvW2n5Hj1VSFweW65BUxmBAX4QpleSMuouV1v7q2Gugv1tD3tY aYElIjElWtF+cZ89jD0JblFZpiZ5OZ+EIsv5MVnI1URDni22sQfEJBuL7XtjH9gN pZNcUPEi2pzTaNXwHR+jQNjQtnyENausldgI29RlKRo1c2aC2bUnmRQpkpdVXNGw jvAtb4QVK85fX50TgY8jx6tVi7mECNFvdd0fVbKBuyVsamp6zLZ077vmiapiN1ML 3VhGd9P+s2zpxqqDww6PObcY4dS7dzA32luz/Nrzmq8WTq/yMXXeHckoLYhF0ROz OdYRGUwSCTvuTlXd6r2M =L69q -----END PGP SIGNATURE-----
Markus Fritsche-4 wrote
the scripts I am using
Thanks! I will have a look... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Ubuntu-ppa-How-is-it-made-tp4819663p4819741.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Markus Fritsche <mfritsche@reauktion.de> writes:
Damien Cassou originally created the scripts I am using. There are a few manual steps involved that can be IMO automated.
Look at https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-vm-core-i386 https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-launcher https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-vm
please update the scripts at https://github.com/pharo-project/pharo-ubuntu instead of having your own repositories. This looks more professional and everybody can find/modify them more easily. The only thing that can't easily be automated I think is the GPG signing. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
participants (4)
-
Damien Cassou -
Markus Fritsche -
Norbert Hartl -
Sean P. DeNigris