You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 4, 2019. It is now read-only.
Why do we need to ship pre-built bar files?
I just did a git pull and it took about half an hour for some reason over my home connection.
NfcSharing is the largest codebase in this repository -- 17MB vs a couple hundred KB for most others.
Can we please strip this out?
Let people load the code and build the bar file.
The text was updated successfully, but these errors were encountered:
I guess we started doing this with good intentions since as at the time we started this new versions of the IDE and device builds had APIS changed that just broke the app as it moved forward. Having a signed build BAR was also useful for people to just download and demo the app if that’s all they wanted to do.
NfcSharing itself has a number of larger images that are part of the assets:/// path since its intent is to demonstrate sharing of images across Bluetooth negotiated by NFC so that’s why the individual BARs are larger.
Happy to review and remove any larger objects that are now redundant if it impacts syncs in locations that have lower bandwidths.
Any thoughts on this from others?
As a corollary I’ve had exactly the same issue with the https://github.com/blackberry/Presentations repo; there’s no way to pick and choose individual presentations and some are large!
Cheers,
John
From: Sean McVeigh [mailto:[email protected]]
Sent: 12 December 2012 04:30
To: blackberry/Cascades-Community-Samples
Subject: [Cascades-Community-Samples] NfcSharing ships an 11MB bar file (#65)
Why do we need to ship pre-built bar files?
I just did a git pull and it took about half an hour for some reason over my home connection.
NfcSharing is the largest codebase in this repository -- 17MB vs a couple hundred KB for most others.
Can we please strip this out?
Let people load the code and build the bar file.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/65.
Research In Motion UK Limited
Registered in England and Wales. Registered No. 04022422, with registered office at 200 Bath Road, Slough, Berkshire, SL1 3XE, United Kingdom
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Why do we need to ship pre-built bar files?
I just did a git pull and it took about half an hour for some reason over my home connection.
NfcSharing is the largest codebase in this repository -- 17MB vs a couple hundred KB for most others.
Can we please strip this out?
Let people load the code and build the bar file.
The text was updated successfully, but these errors were encountered: