CRUX-ARM : Home

Home :: Documentation :: Download :: Development :: Community :: Ports :: Packages :: Bugs :: Links :: About :: Donors

Documentation.MaintainOverlays History

Hide minor edits - Show changes to output

2014-01-29 13:13 by JoseBeneyto -
Changed line 31 from:
The ticket must be tagged as task type: ''Update Request'', and it should contain a brief description of the problem, and all the needed info to reproduce it. Also it would be fine to append all the research info, links, etc we found.
to:
The ticket must be tagged as task type: ''Update Request'', and it should contain a brief description of the problem, and all the needed info to reproduce it. Also it would be fine to append all the research info, useful url links, etc.
2014-01-29 13:13 by JoseBeneyto -
Changed line 31 from:
The ticket must be tagged as task type: Update Request, and it should contain a brief description of the problem, and all the needed info to reproduce it. Also it would be fine to append all the research info, links, etc we found.
to:
The ticket must be tagged as task type: ''Update Request'', and it should contain a brief description of the problem, and all the needed info to reproduce it. Also it would be fine to append all the research info, links, etc we found.
2014-01-29 13:12 by JoseBeneyto -
Changed line 31 from:
The ticket should contain a brief description of the problem, and all the needed info to reproduce it. Also it would be fine to append all the research info, links, etc we found.
to:
The ticket must be tagged as task type: Update Request, and it should contain a brief description of the problem, and all the needed info to reproduce it. Also it would be fine to append all the research info, links, etc we found.
2014-01-29 13:11 by JoseBeneyto -
Changed lines 8-9 from:
This is a brief guide to describe the necessary steps to update a port from an overlay repository
to:
This is a brief guide to describe the necessary steps to update a port from an overlay repository.
Changed lines 11-12 from:
The right order to maintain overlays is: core-arm, opt-arm, xorg-arm, <official-supported_device>-arm, <official-supported_device>-arm, ...
to:
The right order to maintain overlays is: core-arm, opt-arm, xorg-arm, <officially-supported_device>-arm, <officially-supported_device>-arm, ... \\
This means that we should not start with a port from opt-arm if there is a pending update port from core-arm
.
Changed line 15 from:
Get a copy of [[http://crux-arm.nu/gitweb?p=devtools.git;a=summary|devtools.git]] and use checkOverlayUpdates.sh to look for new available updates upstream
to:
Get a copy of [[http://crux-arm.nu/gitweb?p=devtools.git;a=summary|devtools.git]] and use checkOverlayUpdates.sh to look for new available updates upstream:
2014-01-29 13:05 by JoseBeneyto -
Added lines 9-11:

!!!! Considerations
The right order to maintain overlays is: core-arm, opt-arm, xorg-arm, <official-supported_device>-arm, <official-supported_device>-arm, ...
2014-01-29 12:03 by JoseBeneyto -
Added line 16:
[- Note that you must run 'ports -u' before use checkOverlayUpdates.sh to be sure you are up-to-date -]
2014-01-29 12:01 by JoseBeneyto -
Changed line 11 from:
Get a copy of [http://crux-arm.nu/gitweb?p=devtools.git;a=summary|devtools.git] and use checkOverlayUpdates.sh to look for new available updates upstream
to:
Get a copy of [[http://crux-arm.nu/gitweb?p=devtools.git;a=summary|devtools.git]] and use checkOverlayUpdates.sh to look for new available updates upstream
2014-01-29 12:01 by JoseBeneyto -
Changed line 11 from:
Check for new available updates upstream
to:
Get a copy of [http://crux-arm.nu/gitweb?p=devtools.git;a=summary|devtools.git] and use checkOverlayUpdates.sh to look for new available updates upstream
2014-01-29 11:59 by JoseBeneyto -
Added lines 4-5:

[[<<]]
2014-01-29 11:58 by JoseBeneyto -
Added lines 5-8:
!!!! Introduction
This is a brief guide to describe the necessary steps to update a port from an overlay repository

!!!! Steps
2014-01-29 11:56 by JoseBeneyto -
Changed line 17 from:
However, if something must be adapted to ARM devices then it will need more research and development.
to:
However, if something must be adapted to ARM devices then it will need more work.
2014-01-29 11:54 by JoseBeneyto -
Deleted line 3:
[[<<]]
2014-01-29 11:54 by JoseBeneyto -
Changed lines 20-21 from:
At the end, if we can't update the port overlay then we should file a ticket with all the research progress we made. The ticket should contain a brief description of the problem, and all the needed info to reproduce it. Also it would be fine to append all the research info, links, etc we found.
to:
At the end, if we can't update the port overlay then we should file a ticket with all the research progress we made. \\
The ticket should contain a brief description of the problem, and all the needed info to reproduce it. Also it would be fine to append all the research info, links, etc we found.
2014-01-29 11:53 by JoseBeneyto -
Changed line 13 from:
For this case we should go to CRUX upstream's gitweb interface:
to:
For this case we should go to CRUX upstream's gitweb interface:\\
Changed line 16 from:
If upstream changes are trivial as increment the version number, then apply the same difference to the Pkgfile and build the port:
to:
If upstream changes are trivial as increment the version number, then apply the same difference to the Pkgfile and build the port:\\
2014-01-29 11:53 by JoseBeneyto -
Changed line 6 from:
* Check for new available updates upstream
to:
Check for new available updates upstream
Changed line 12 from:
* If there are available updates we must to know the differences applied upstream. \\
to:
If there are available updates we must to know the differences applied upstream. \\
Changed line 16 from:
* If upstream changes are trivial as increment the version number, then apply the same difference to the Pkgfile and build the port:
to:
If upstream changes are trivial as increment the version number, then apply the same difference to the Pkgfile and build the port:
Changed line 20 from:
* At the end, if we can't update the port overlay then we should file a ticket with all the research progress we made. The ticket should contain a brief description of the problem, and all the needed info to reproduce it. Also it would be fine to append all the research info, links, etc we found.
to:
At the end, if we can't update the port overlay then we should file a ticket with all the research progress we made. The ticket should contain a brief description of the problem, and all the needed info to reproduce it. Also it would be fine to append all the research info, links, etc we found.
2014-01-29 11:52 by JoseBeneyto -
Changed line 7 from:
sepen@cubieboard2:~/devel/crux/devtools $ ./checkOverlayUpdates.sh core-arm
to:
$ checkOverlayUpdates.sh core-arm
Changed lines 13-15 from:
For this case we should go to http://crux.nu/gitweb/?p=ports/core.git;a=commitdiff;h=53bc70dfcd7e28cc2996e7e2e0bda297fe955588

* If upstream changes are trivial as increment the version number, then apply the same difference to the Pkgfile and build the port (http://crux-arm.nu/gitweb?p=ports/core-arm.git;a=commitdiff;h=65ff2db684cdd1de1ab24cb517d2b7dc56bd4ac9). However, if something must be adapted to ARM devices then it will need more research and development.
to:
For this case we should go to CRUX upstream's gitweb interface:
http://crux.nu/gitweb/?p=ports/core.git;a=commitdiff;h=53bc70dfcd7e28cc2996e7e2e0bda297fe955588

* If upstream changes are trivial as increment the version number, then apply the same difference to the Pkgfile and build the port:
http://crux-arm.nu/gitweb?p=ports/core-arm.git;a=commitdiff;h=65ff2db684cdd1de1ab24cb517d2b7dc56bd4ac9 \\
However, if something must be adapted to ARM devices then it will need more research and development.
2014-01-29 11:50 by JoseBeneyto -
Changed line 15 from:
* If upstream changes are trivial as increment the version number, then apply the same difference to the Pkgfile and build the port. However, if something must be adapted to ARM devices then it will need more research and development.
to:
* If upstream changes are trivial as increment the version number, then apply the same difference to the Pkgfile and build the port (http://crux-arm.nu/gitweb?p=ports/core-arm.git;a=commitdiff;h=65ff2db684cdd1de1ab24cb517d2b7dc56bd4ac9). However, if something must be adapted to ARM devices then it will need more research and development.
2014-01-29 11:45 by JoseBeneyto -
Changed lines 1-3 from:
==Maintain Overlays==

1.
Check for new available updates upstream
to:
!!Documentation

!!!
Maintain Overlays
[[<<]]

*
Check for new available updates upstream
Changed lines 12-16 from:
2. If there are available updates we must to know the differences applied upstream. For this case we should go to http://crux.nu/gitweb/?p=ports/core.git;a=commitdiff;h=53bc70dfcd7e28cc2996e7e2e0bda297fe955588

3. If upstream changes are trivial as increment the version number, then apply the same difference to the Pkgfile and build the port. However, if something must be adapted to ARM devices then it will need more research and development.

4. At the end, if we can't update the port overlay then we should file a ticket with all the research progress we made. The ticket should contain a brief description of the problem, and all the needed info to reproduce it. Also it would be fine to append all the research info, links, etc we found.
to:
* If there are available updates we must to know the differences applied upstream. \\
For this case we should go to http://crux.nu/gitweb/?p=ports/core.git;a=commitdiff;h=53bc70dfcd7e28cc2996e7e2e0bda297fe955588

* If upstream changes are trivial as increment the version number, then apply the same difference to the Pkgfile and build the port. However, if something must be adapted to ARM devices then it will need more research and development.

* At the end, if we can't update the port overlay then we should file a ticket with all the research progress we made. The ticket should contain a brief description of the problem, and all the needed info to reproduce it. Also it would be fine to append all the research info, links, etc we found.
2014-01-29 11:41 by JoseBeneyto -
Changed line 1 from:
== Maintain Overlays ==
to:
==Maintain Overlays==
2014-01-29 11:40 by JoseBeneyto -
Added lines 1-13:
== Maintain Overlays ==

1. Check for new available updates upstream
sepen@cubieboard2:~/devel/crux/devtools $ ./checkOverlayUpdates.sh core-arm
Results for overlay: core-arm
PORT VERSION UPSTREAM
util-linux 2.24-1 2.24.1-1 (core)

2. If there are available updates we must to know the differences applied upstream. For this case we should go to http://crux.nu/gitweb/?p=ports/core.git;a=commitdiff;h=53bc70dfcd7e28cc2996e7e2e0bda297fe955588

3. If upstream changes are trivial as increment the version number, then apply the same difference to the Pkgfile and build the port. However, if something must be adapted to ARM devices then it will need more research and development.

4. At the end, if we can't update the port overlay then we should file a ticket with all the research progress we made. The ticket should contain a brief description of the problem, and all the needed info to reproduce it. Also it would be fine to append all the research info, links, etc we found.