ADHOC/replicant-vendor_replicant
3
0
Fork 0
Code Issues 6 Pull Requests Releases Activity
892 Commits 2 Branches 0 Tags 430 MiB
CSS 35.3%
JavaScript 25.2%
Shell 21.2%
C# 8.4%
Makefile 7.8%
Other 2%
cfe876cefb
Go to file
PaulW cfe876cefb Update backuptool.sh to correctly process force_backuptool flag/file. 
This is regarding the following patch:
5cdb4ec653

The patch which was to allow custom_backup_list.txt to be maintained while flashing via ROMManager
WHILE the flag/file force_backuptool is set/present still has issues.  There are 2 reasons for this.

1) The flag is only checked during the first pass (backuptool.sh backup), as once /etc/force_backuptool
   is known to exist, all files are moved to /tmp/backupdir as designated, but when the script is
   ran again once /system has been wiped and updated, the file /etc/force_backuptool no longer exists
   as it was moved to /tmp/backupdir/force_backuptool, so the script fails as it is not checking that
   location.

2) When the backuptool.sh script is called, the above function (checking for force_backuptool) is called
   *before* the /system partition is mounted.  This therefor ignores the file regardless of whether it
   exists or not.  This is caused by check_installscript being called at the wrong point of the script.

There are therefor 2(two) main changes to this script to allow the force_backuptool override to work.
The first being within the main function of check_installscript, and the second being the location of
where check_installscript is called (ie, I moved it to below check_prereq call in the case statement,
as mounting is called before the check_prereq function checks if the ROM version is the same).

This affects *all* devices.

Change-Id: Ia7438f396eaa91b0723e56bb32ce98725e2b2025
2011-05-17 17:49:39 +01:00
overlay Mecha: Add overlay configs in vendor 2011-05-06 04:21:02 -04:00
prebuilt Update backuptool.sh to correctly process force_backuptool flag/file. 2011-05-17 17:49:39 +01:00
products vega: update fingerprint 2011-05-14 16:41:27 +09:00
tools Fix LeoUpdate script so that only one boot folder is present 2011-03-27 17:23:20 +05:30
.gitignore gitignore 2010-06-27 20:11:11 -07:00
Android.mk bash ncurses nano are now built. ADWLauncher now properlyi overrides Launcher and Launcher2 2010-07-07 23:48:50 -07:00
CHANGELOG Move CHANGELOG 2010-07-05 03:43:39 +00:00
CHANGELOG.mkdn Update Hero maintainer 2011-05-11 12:19:36 +01:00
extract-gapps-files Add a script to extract gapps files from downloaded zip file. 2010-10-29 23:49:13 +08:00
extract-google-files Remove crap from the CYANOGEN_WITH_GOOGLE build. 2010-10-10 01:17:59 -04:00
get-google-files Remove the obsolete gb-tegra GApps 2011-03-16 01:47:53 -05:00
get-rommanager follow redirects on curl 2011-03-29 10:16:51 -07:00
LICENSE Add LICENSE file 2011-01-30 21:10:08 -05:00
prelink-linux-arm-hero.map HERO: updated prelink map 2011-01-24 10:56:26 +11:00
prelink-linux-arm-msm722x.map cm: Clean up prelink maps 2011-01-18 00:54:37 -05:00
README.mkdn cm: Update README 2011-01-16 03:57:45 -06:00
vendorsetup.sh Mecha: Add mecha to the cyanogen vendor 2011-04-30 18:11:26 -04:00

README.mkdn

CyanogenMod

Submitting Patches

Patches are always welcome! Please submit your patches via CyanogenMod Gerrit! You can do this by using these commands:

(From root android directory)
. build/envsetup.sh
(Go to repo you are patching, make your changes and commit)
cmgerrit <for(new)/changes(patch set)> <branch/change-id> 

repo start gingerbread .
(Make your changes and commit)
repo upload .

Note: "." meaning current directory For more help on using this tool, use this command: repo help upload

Make your changes and commit with a detailed message, starting with what you are working with (i.e. vision: Update Kernel) Commit your patches in a single commit. Squash multiple commit using this command: git rebase -i HEAD~<# of commits>

To view the status of your and others' patches, visit CyanogenMod Code Review

Getting Started

To get started with Android/CyanogenMod, you'll need to get familiar with Git and Repo.

To initialize your local repository using the CyanogenMod trees, use a command like this:

repo init -u git://github.com/CyanogenMod/android.git -b gingerbread

Then to sync up:

repo sync

Please see the CyanogenMod Wiki for building instructions.

For more information on this Github Organization and how it is structured, please read the wiki article

Buildbot

All supported devices are built nightly and periodically as changes are committed to ensure the source trees remain buildable.

You can view the current build statuses at buildbot.teamdouche.net