Sugar For Mac

Posted on |



  1. Sugarsync Mac
  2. Sugar For Macarons

MAC Sugar Dada Dupes Here are our dupes for MAC Sugar Dada, which is a moderately warm-toned, medium copper with a semi-matte finish. It is a limited edition. Too much sugar is too much, no matter the source. It all comes down to how fast the sugars get absorbed. For example, your body spends more time digesting an apple because of the fiber content, so the natural sugar absorbs more slowly. On the flip side, the added sugar in soda arrives all at once in your system like a sugar bomb. Sugar by Process.Audio is a Virtual Effect Audio Plugin for macOS and Windows. It functions as a VST Plugin, an Audio Units Plugin, a VST 3 Plugin and an AAX Plugin.

me

english | español | français | norskHowTo[ID# 102830]


Are you new to Sugar?

The SoaS download is found here: Sugar on a Stick. Basic instructions are found below:

Sugar on a Stick installation instructions

MS Windows


  1. Prepare: Download the Fedora Live USB Creator from FedoraHosted.
  2. Download the latest Sugar on a Stick .iso file.
  3. Load: Insert a USB flash drive (or SD Card) with 2 GB or more of free space into your computer and launch Fedora Live USB Creator to create a Sugar-on-a-Stick bootable image.
    Note: Be sure to set the persistent storage slider to a non-zero value.
  4. Boot: Insert the USB stick into a USB port on your computer. Set the option to 'boot from USB' in your computer's BIOS setup, and then start up the computer.

Detailed installation instructions for Windows and booting instructions are available. There is also a guide to exploring Sugar.

GNU/Linux



  1. Download the latest Sugar on a Stick .iso file.
  2. Prepare: (with root user permissions at a terminal or console command line)
    • Create a mount point directory: mkdir /run/soas
    • Mount the .iso file to make it accessible as a disk: mount /path/to/downloaded.iso /run/soas/
      (Where /path/to/downloaded.iso is the filesystempath, or fully specified name, of the downloaded .iso file.)
      This is the source for the installation, and must remain mounted until the installation is complete.
    • Insert a USB stick of 2 GB or greater capacity into your computer.
    • With root user permissions at a terminal or console command line, use the command sudo df -Th or sudo blkid to get the USB device node name.
      • (Items in angle brackets, such as <MyAccount> are descriptive placeholders.)
      You should see something like the following:
      (The /run/media/<MyAccount>/ path is the standard mount point for removable media.
      /media/<MyMountPoint> is common on other operating systems.)
      (Additional disk drive partitions may be listed on your computer.)
      The mount point (Mounted on), Filesystem, Size, and LABEL should help you identify what you want.
    • Unmount the USB device filesystem:
      umount /run/media/<MyAccount>/<MyUSBdiscMountPoint>
      (The /run/media/<MyAccount>/ path is the standard mount point. Other operating systems may use /media/<MyMountPoint>.)
    • (You should have the isomd5sum package installed so that the following installation script can verify the download.)
  3. Load: Execute the following installation command, as the root user, in one command line with many options:
    /run/soas/LiveOS/livecd-iso-to-disk --reset-mbr --overlay-size-mb 500 --home-size-mb 500 --unencrypted-home /path/to/downloaded.iso /dev/sd?1
    The '?' in the final parameter represents the target USB device scsi drive node, such as sdb1 or sdc1, etc., and /path/to/downloaded.iso is the location and name of the .iso file.
    The operating system will occupy ~960 MB, and the overlay and home size arguments, 500 and 500, were selected to fit in a 2 GB device. These may be adjusted depending on your preferences and device capacity (see LiveOS image). On a 4 GB device, one might use 1000 and 1600 for the size arguments.
    The installation transcript should look something like the following:

  4. Boot: Insert the USB stick into a bootable USB port on your computer. Set the option to 'boot from USB' in your computer's BIOS setup, and then start up the computer.
  • To create more Sugar Sticks on other 2 GB or greater USB or SD devices, while running Sugar on a Stick, one may run the Terminal Activity, and execute this command as the root user:
    livecd-iso-to-disk --reset-mbr --overlay-size-mb 500 --home-size-mb 500 --delete-home --unencrypted-home /run/initramfs/livedev /dev/sd?1
Replace /dev/sd?1 with a new device node for the second USB/SD device that you want to load with Sugar on a Stick.

Detailed installation instructions for GNU/Linux and booting instructions are available. There is also a guide to exploring Sugar.GNU/Linux users may also want to install the Sugar packages on their favorite distro, apart from Sugar on a Stick.

Mac

Apple Mac OS X


The instructions below are based on the Ubuntu Web page at <http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-mac-osx>.

  1. Prepare: These instructions are for 32-bit and 64-bit processors.
  2. Download the latest Sugar on a Stick .iso file.
  3. Load:
    Here is a simple way to load a bootable USB on a Mac.
    1. Enter the Terminal: /Applications/Utilities/Terminal.
    2. Type diskutil list. You should see all the disk drives you have inserted into your computer.
    3. Insert the disk drive to which you want to write Sugar on a Stick.
    4. Type diskutil list again. You should see that your USB drive has been added to the list. If not, wait a while and repeat.
    5. Type hdiutil convert -format UDRW -o <Sugar on a Stick image file>.img <Sugar on a Stick image file> to convert the image into a bootable format.
    6. Type sudo diskutil unmountDisk <device name> to unmount the disk (it will not be ejected).
    7. Type sudo dd if=<Sugar on a Stick image file>.img.dmg of=<device name> bs=1m. sudo will ask for your password, and then dd will start writing the disk file.
    8. When dd finishes writing the disk file, type sudo diskutil eject <device name>.
  4. Boot: Insert the USB stick into a USB port on your computer, then reboot and press and hold the Option key while rebooting. You should see a list of all the EFI-recognizable USB drives that can be bootstrapped. If Sugar on a Stick is not one such drive, it cannot be bootstrapped: you need rEFInd (a fork of rEFIt).


  • Have a MacBook? Consider these options:
Bootable CD of Trisquel 4.5 for MacBook Air
See other installation variations at Sugar Creation Kit
  • Have an iBook or PowerPC Mac?
See Ubuntu/PPC and fedora:Architectures/PowerPC.

Alternative installation instructions for Mac OS X. Also, these older installation instructions and booting instructions may be consulted.
There is also a guide to exploring Sugar.

Advanced users

Do you have an OLPC XO?

  • Upgrade to the latest olpc:Releases from OLPC (which may require a developer key).
  • Experiment with Updating XOs to the latest Sugar on a Stick release.


Some alternate installations

  • Once you download, and then burn or load a Sugar on a Stick (SoaS) .iso file, and boot it, the running Fedora 30 SoaS Live CD/USB may be used to install Fedora with Sugar to a hard disk or a 4 GB USB stick with the liveinst command.
- You start with a SoaS LiveOS image, and then load an uncompressed version onto the hard disk or USB stick.


  • If you have a high-speed Internet connection,
    Fedora with the Sugar graphical learning environment may be installed to a hard disk or a a 4 GB USB stick with a Netinstall CD.
- Not a compressed LiveOS image like SoaS, but all of Sugar.
- This requires a high-speed Internet connection for software component downloading during installation.

Do you use GNU/Linux?

Sugar is supported by several GNU/Linux distributions. Sugar Labs does not support any specific distribution, but does focus development on Fedora and Debian, which helps SoaS and Ubuntu.

LogoNameNotes
Sugar on a StickLive system of the Sugar Learning Environment
FedoraFedora 30
UbuntuUbuntu 18.04 Bionic
DebianDebian Stretch, see also Live Build
OLPC OS 16.04OLPC OS for OLPC NL3 laptops based on Ubuntu 16.04 Xionic
OLPC OS 13.xOLPC OS for OLPC XO laptops based on Fedora 18
openSUSEPart of an Linux for Education (Li-f-e) series
Trisquel ToastBased on Ubuntu
Please note:
  • Development changes occur rapidly, and the text here lags the current state of systems development.
  • For the latest information on any development project, visit their work sites.


Are you a developer?

Please see this developer documentation website for the sugar-build development environment.


Some additional references you may find useful:

  • See https://github.com/sugarlabs/,
  • Gitorious source code repository,
  • The Supported systems page,
  • Sweets, to launch Sugar using the Sugar Package Management System,
  • Virtual machine or emulator image files,
  • Adding Sugar to your favorite distro...


Virtual Machines on all platforms

VirtualBox Appliances


More Virtual Appliances


Sugar included in other GNU/Linux operating systems, and older versions.

Also includes some VMware Player Appliances

If you run into problems, you may want to consult the Talk:VirtualBox page for help.

Are you preparing a deployment without Internet access?

See Sugar Creation Kit

Sugarsync Mac


Are you looking for Sugar Activities?

Visit the Sugar Activity Library<imagemap>

File:Sugarlabs_mainpage_02.pngrect 14 14 38 47 Calculaterect 74 15 107 44 Chatrect 137 16 171 43 Imploderect 201 14 238 46 Distancerect 265 12 298 47 Etoysrect 11 79 41 108 Moonrect 74 78 106 110 Paintrect 140 78 170 109 Pippyrect 201 80 235 108 Readrect 266 82 298 107 Recordrect 11 143 41 172 TamTam Synth Labrect 75 146 105 169 Terminalrect 142 140 166 173 Turtle Blocksrect 201 144 235 171 WikiBrowserect 269 142 299 173 Writedefault Sugar Activity Librarydesc none</imagemap>

Retrieved from 'https://wiki.sugarlabs.org/index.php?title=Downloads&oldid=102830'

Overview

Sugar's Mobile Application Configuration Service (MACS) enables partners and eligible customers (i.e. Enterprise and Ultimate) to create and distribute custom-branded versions of the Sugar Mobile app. Before downloading your app from MACS for distribution, you must provide MACS with a certificate and other information in order to digitally sign the app. App signing allows the client (i.e. phone or tablet running your app) to identify who signed the app and to verify that it has not been modified since you signed it. The certificate serves as a virtual fingerprint that uniquely associates the app to you. This also helps iOS and Android ensure that any future updates to your app are authentic and come from the original author.

For more information on using MACS, please refer to the Mobile Application Configuration Service User Guide.

Mac

Prerequisites

To use MACS, you must be in one of the following authorized user groups:

  • Customers running a supported version of Sugar Sell, Serve, Enterprise, or Ultimate.
  • SugarCRM's OEM partners (for use and distribution with their authorized OEM solution)

Note: SugarCRM partners who are creating a re-branded mobile app for a customer must log in and do so only under that customer's account. Partners are not authorized to create and store these apps under their own Sugar accounts.

Steps to Complete

App Signing for iOS

There are multiple steps you need to take to successfully app sign for iOS before you will be able to distribute the application via the Apple App Store, an internal enterprise store, or an MDM account. The following sections describe each of these steps in detail. For more details on any of the steps, please refer to the Apple Developer documentation on Apple's developer site.

Registering an Apple Developer Account

Apple offers two levels of developer accounts: Individual or Enterprise. An Enterprise account allows you to distribute applications internally or via an MDM vendor in addition to distributing via the public store. An Individual account only allows you to distribute via the public store. Decide which option is right for you, navigate to Apple's developer site, click 'Create Apple ID', and follow the instructions to register for your Apple developer account.

Installing Apple Certificates

Your keychain must contain Apple root and intermediate certificates in order to successfully generate a signing certificate. Apple certificates are automatically installed when you install Xcode. If you do not have Xcode installed or if you do not wish to have it installed on your computer, then you must download the required certificates from the Apple PKI page on Apple's website.

Sugar For Macarons

Generating a Signing Certificate

Once the Apple certificate is installed on your computer, you can begin generating a signing certificate. To do this:

  1. Log into your Apple developer account.
  2. Navigate to the Certificates, Identifiers, & Profiles section.
  3. Click 'All' under the Certificates panel on the left then click the Plus icon to create a new iOS certificate.
  4. From this page, select a certificate type:
    • Development certificates do not allow publishing to stores but are useful if you wish to install and test the app on your device. Select 'iOS App Development' to create a testing certificate.
    • A production certificate (a.k.a. distribution certificate) is required if you want to publish your app to stores. Depending on your developer account type, there are two different options for production certificates:
      • App Store and Ad Hoc : This option is visible for users with an Individual developer account type. Select 'App Store and Ad Hoc' to create a distribution certificate.
      • In-House and Ad Hoc : This option is visible for users with an Enterprise developer account type. Select 'In-House and Ad Hoc' to create a distribution certificate.
  5. After selecting the certificate type that is best for your situation. Click 'Next', and follow Apple's instructions for creating, uploading, and approving a certificate request. You will then see it available for download in the Certificates section.
  6. Download the new certificate and install it onto your keychain. To do this, click 'Download' to download the certificate onto your Mac computer then double-click on the file.
  7. Open your Downloads folder then right-click on the file and select 'Keychain Access' from the Open With menu to install the certificate into your Keychain.
    You should now see the certificate in the Keychain application:
  8. Export the certificate in .p12 format by right-clicking the certificate's name via the Keychain list and selecting 'Export…' from the menu.
  9. From the Export File dialog, enter a name for the certificate and then select 'Personal Information Exchange (.p12)' as the file format.
  10. Click 'Save' to save the file to your local file system.

Creating an Application ID

With the certificate successfully saved on your computer, you can begin creating an application ID. The app ID is a string that contains a team ID and a bundle ID which is used to identify one or more apps from a development team. The following steps explain how to create a unique app ID.

  1. Log into your Apple developer account.
  2. Navigate to the App IDs section and click the Plus icon to create a new ID.
  3. Enter your app's name in the Name field and specify an application ID in the Bundle ID field according to Apple's guidelines. Please note that if you are planning to use in-house distribution, then you must select the radio button for 'Explicit App ID'. You can also enter a wildcard app ID if you have multiple apps and wish to use one provisioning profile for multiple app IDs. For more information on wildcard IDs, please refer to the iOS Developer documentation.
  4. At the bottom of the page, click 'Continue' to view the confirmation page.
  5. Finally, click 'Register' to finalize and confirm your app ID.

Generating a Provisioning Profile

Once you have created the app ID, it is time to create a provisioning profile. This is necessary for installing development applications on iOS devices. To generate a development or distribution provisioning profile:

  1. Log into your Apple developer account.
  2. Navigate to the Provisioning Profiles section and click the Plus icon to create a new provisioning profile.
  3. From this page, select a provisioning profile type:
    • Development profiles do not allow you to publish to stores but are useful if you wish to install and test the app on your device. Select 'iOS App Development' to create a testing profile.
    • A distribution profile is required if you want to publish your app to stores. Depending on your developer account type, there are two different options for distribution profiles:
      • App Store : This option is visible for users with an Individual developer account type. Select 'App Store' to create a distribution profile.
      • In-House : This option is visible for users with an Enterprise developer account type. Select 'In House' to create a distribution profile.

      • Ad-Hoc : This option is also visible for users with an Enterprise developer account type. If you wish to only install your app on specific devices, select 'Ad-Hoc'. For more information on this, please refer to the About Ad Hoc Provisioning Profiles page in Apple's App Distribution Guide.
  4. After selecting the appropriate profile type, click 'Continue'.
  5. On the Configure page, select the app ID you created in the Creating an Application ID section then click 'Continue'.
  6. On the next page, select the certificate you created in the Generating a Signing Certificate section then click 'Continue'.
  7. If you selected a development profile or an ad hoc distribution profile in step two, there will be an additional step where you must select the allowed iOS devices. This ensures the signed app can only be installed on the given phones or tablets. Click 'Continue' to move to the next page.
    Note: You must have already registered these devices in the Devices section prior to generating the profile.
  8. Enter the desired profile name in the Profile Name field and click 'Continue'.
  9. Finally, click 'Download' to download the profile to your computer.

You now have your certificate and profile files ready to upload to MACS in order to sign the iOS app. For detailed information about signing identities, please refer to the Maintaining Your Signing Identities and Certificates article in Apple's Distribution Guide.

App Signing for Android

Before you can distribute the application to the Google Play Store, an internal enterprise store, or an MDM account, you must first app sign for Android. This section will provide information on how to register for an Android Developer account and how to generate an Android signing certificate.

Registering an Android Developer Account

If you wish to distribute your app via the Google Play store, you must first register an Android Developer Account. To do this, navigate to the Android Developers Portal, and follow the instructions. For more information, please refer to the Get Started with Publishing documentation on the Android developer site.

Generating a Signing Certificate

Prior to distributing an Android app to mobile devices via any method, you must generate a signing certificate using the Java keytool command interface utility. Keytool is part of Java development kit (JDK) and is available as part of JDK installation and Android SDK. For more information on acquiring the utility, please refer to Oracle's Java SE Downloads article or the Android Developer Guide.

Once the keytool utility is available on your computer, you can then easily generate your certificate which will then be stored in your keystore file. To do this, simply run the following command from the command-line:

The following arguments are used by the keytool utility:

  • <keystore-name> : File name of the resulting keystore
  • <alias> : Alias name of the entry to process
    Note: The alias name for your keystore must be set     to 'key'.
  • <key-algorithm> : The key algorithm name
    Note: The key algorithm must be set to 'RSA'.
  • <keysize> : Key bit size
    Note: The key size must be set to 2048.
  • <days-valid> : Number of days your app is valid

In the following example, the command-line keytool utility will generate the keystore as a file called my-release-key.keystore with a single key that will be valid for 10,000 days:

Once you run this command, the keytool will prompt you to specify the keystore password and key password, along with a request for additional information (e.g. First and Last Name). Please note that MACS requires that the keystore and the key passwords be the same.

For more instructions on how to sign your app for Android, please refer to the Sign Your App page on the Android developer site.

Note: After submitting a signed app to Google Play, you must use that same signing certificate for all future updates. If you change the certificate, Google Play will not recognize the app as a new version of the same application, and users will not be able to update. If you lose the signing certificate, you will have to register a new app in Google Play.

Additional Resources

More information about app-signing procedures and requirements is available directly from the iOS and Android developer sites:

Last modified: 2020-01-22 21:26:00