Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
package-helpers
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
trisquel
package-helpers
Commits
2036d2ee
Commit
2036d2ee
authored
9 years ago
by
Santiago Rodriguez
Browse files
Options
Downloads
Patches
Plain Diff
README.md : updated to show the current workflow
parent
54664cce
No related branches found
Branches containing commit
No related tags found
1 merge request
!109
Update docs
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+23
-14
23 additions, 14 deletions
README.md
with
23 additions
and
14 deletions
README.md
+
23
−
14
View file @
2036d2ee
## Introduction
This set of scripts are helpers that modify and c
ompile thos
e packages coming
This set of scripts are helpers that modify and c
reate the sourc
e packages coming
from the Ubuntu upstream which need it. It might be because they contain
non-free stuff, references to Ubuntu that need to be changed, or because we
want the package to work our way.
...
...
@@ -9,20 +9,29 @@ This helpers are similar to some of those in the [gNewSense](http://www.gnewsens
some ideas and even some lines from them. If you plan to build an Ubuntu
derivative of your own, we suggest you to use Builder instead of this helpers.
All packages in this list are in the appropriate blacklist in the repository
updater, so they never enter into the repo from upstream and need to be
compiled with this helpers and pushed into reprepro. This helpers also need
to be run by hand - and the results tested - any time the repo watchdog warns
about pending updates from upstream.
Once a new package is added, it takes priority over the original one from Ubuntu,
so they never enter into the repo from upstream and need to be
compiled with this helpers and pushed into reprepro.
To add a package to the list, just copy one -
`make-apache2`
is a good template -
and rename it to
`make-sourcePackageName`
. To send the file back to us, or to
include any modification into the current scripts, use
`bzr diff`
and send
the output as an attachment to trisquel-devel@listas.trisquel.info. You need
to join the mailing list to send messages to it.
To add a package to the list, follow the
[
CONTRIBUTING
](
https://devel.trisquel.info/trisquel/package-helpers/blob/belenos/CONTRIBUTING.md
)
guidelines.
## Steps
Those are the steps done by the helpers:
1.
Create local apt configuration, so you don't need to be root to run the helpers
2.
Get the ubuntu and trisquel gpg keys
3.
Get the source packages from their original repo
4.
Uncompress them
5.
Apply the changes described in the helper
6.
Re-package it, adding "triquel$VERSION" version string
## Recommendations
*
You don't need to use sudo in order to run those scripts, but some extra packages are needed:
`sudo apt-get install dpkg-dev sed git rpl devscripts quilt patch`
*
Take care to use the right sourcePackageName, many source packages produce
several binary packages.
`apt-cache showsrc binary-package`
can help you.
*
If possible, use sed to replace chains in the upstream source without the
...
...
@@ -32,9 +41,8 @@ it at the `DATA/sourcePackageName` directory
would actually be shown to the user. Avoid replacing copyright statements!
*
Try to write your replacements in a way they might work in future versions
of the upstream package. Well written regexps and sed will help with that.
*
Some of this packages require the lsb to match Trisquel values. Edit the
`/etc/lsb_release`
accordingly, or run the helpers in a Trisquel box.
*
You can - and maybe should - run this scripts inside a chroot.
*
You can test your changes by doing them inside the _PACKAGES/sourcePackageName/source/_ directory,
and running
`dpkg-source -b .`
, before being added to the helper script
## Netinstall
...
...
@@ -54,3 +62,4 @@ To generate the images, we run the following scripts:
Then we push the results into the Trisquel repository and run the script
`make-debian-installer`
to build the final images.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment