forked from davidbannon/libqt5pas
-
Notifications
You must be signed in to change notification settings - Fork 0
/
package.readme
55 lines (37 loc) · 1.23 KB
/
package.readme
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
package.readme
On a suitably setup machine, eg
apt install devscripts rpm rpmlint
Pull down the code from gitlab,
cd cbindings
refresh source (use a script that gets only relevent files from Lazarus -
$> bash ./refresh.bash
$> cd cbindings;
## remove any existing library and symlinks
$> qmake -qt=qt5; make (wait ....)
$> cd package;
## update the whatsnew file, maybe from Z's commits.
## remove any existing packages
$> DEBEMAIL=YOUR-EMAIL-ADDRESS bash ./package-lib
Then do a git add, commit and push as necessary.
From github page, make new release, upload as necessary, release.
---------- Legacy Methods, disregard ----------------
make <enter>
(wait awhile)
strip libQt5Pas.so.1.2.8
update the version file
cd package
bash ./deb-package
bash ./rpm-package
test
Easy to let github tag the release, create the Release Page, assign an
appropriate tag and it will be created when Release is released.
# back in the top level dir _
# git tag -a v1.2.8
# git push --tags
In the github page, 'releases', 'draft new release'.
Some text, add the generated packages, 'publish'.
back in packages :
rm *.deb *.rpm *.gz
Maybe clean up the working directories ...
rm -Rf tmp
Must update every 60 days to keep workflow running.