Re: [DNG] my first two packages
$ gpg import-orig ../epoch_1.3.0.tar.bz2 I rectify: $ gbp import-orig ../epoch_1.3.0.tar.bz2 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] my first two packages
il devuanizzato Aitor il 19-01-20 11:06:26 ha scritto:
Hi again,
Here you are my first packaging attempt:
experimental-epoch_1.3.0
Download the sources and follow the steps bellow:
- Create your own gpg signature key.
- Create a folder named epoch and go into it.
- Generate an empty git repository and import the project using
git-buildpackage:
$ git init
$ git config --global user.name "viverna"
$ git config --global user.email "vive...@inventati.org"
$ gpg import-orig ../epoch_1.3.0.tar.bz2
Enter the name of the project and its version.
- Now yo can build the project:
$ git-buildpackage -j4 -tc -k
--git-export-dir="../build-area" --git-tag --git-ignore-branch
being the public part of your gpg key.
Once you've built it, you can import the whole project using
git-builtpackage again via:
$ gbp import-dsc ../epoch_1.3.0.dsc
As an exercise, you can include all the defined conditionals in the
buildepoch.sh script (I *removed* this file!) in the Makefile by the
following way:
ifeq ()
endif
https://www.gnu.org/software/make/manual/html_node/Conditional-Example.html#Conditional-Example
I'll study this part in the next month.
You could fuse both projects in an unique source defining two separate
packages in the control file, but they have different version numbers.
Keep it in mind.
I do not think so.
epoch init-system change rarely, config file will be added in the
project faster.
Cheers,
Aitor.
--
_
< Viverna >
-
\^/^
\ / \ // \
\ |\___/| / \// .\
\ /0 0 \__ /// | \ \ **
/ / \/_/// | \ \ \ |
@_^_@`/ \/_ //| \ \ \/\ \
//_^_/ \/_ // |\\ \ \
( //) |\/// | \ \ | |
( / /) | // | \ _\ | /
( // /) | ; -.|_ _\.-~ / /
(( / / )) |_ *-.|.-~-. .~~
(( // / ))\ / ~-. _ .-~ /
(( /// )) `. }{ /
(( / )) .~-.\\-` .~
///...<\ _ -~
///-._ _ _ _ _ _ _{^ - - - - ~
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] my first two packages
Hi again, On 18/1/20 20:16, viverna wrote: il devuanizzato Aitor il 18-01-20 11:48:58 ha scritto: My short answer for now: - Use lowercase letters for the debian folder. A DEBIAN folder with uppercase letters will be created within each generated packages. "DEBIAN" uppercase is required from `dpkg-deb -b`: " Creates a debian archive from the filesystem tree stored in binary-directory. binary-directory must have a DEBIAN subdirectory, which contains the control information files such as the control file itself." I don't create package with Debian normal method documented, I don't understand how make good package. - Create a debian/rules file. This file is paramount, but it's missing! I insert rules file. I will commit soon. Hope this helps, Aitor. Thanks Aitor. Here you are my first packaging attempt: experimental-epoch_1.3.0 Download the sources and follow the steps bellow: - Create your own gpg signature key. - Create a folder named epoch and go into it. - Generate an empty git repository and import the project using git-buildpackage: $ git init $ git config --global user.name "viverna" $ git config --global user.email "vive...@inventati.org" $ gpg import-orig ../epoch_1.3.0.tar.bz2 Enter the name of the project and its version. - Now yo can build the project: $ git-buildpackage -j4 -tc -k --git-export-dir="../build-area" --git-tag --git-ignore-branch being the public part of your gpg key. Once you've built it, you can import the whole project using git-builtpackage again via: $ gbp import-dsc ../epoch_1.3.0.dsc As an exercise, you can include all the defined conditionals in the buildepoch.sh script (I *removed* this file!) in the Makefile by the following way: ifeq () endif https://www.gnu.org/software/make/manual/html_node/Conditional-Example.html#Conditional-Example You could fuse both projects in an unique source defining two separate packages in the control file, but they have different version numbers. Keep it in mind. Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] my first two packages
il devuanizzato Aitor il 18-01-20 11:48:58 ha scritto: My short answer for now: - Use lowercase letters for the debian folder. A DEBIAN folder with uppercase letters will be created within each generated packages. "DEBIAN" uppercase is required from `dpkg-deb -b`: " Creates a debian archive from the filesystem tree stored in binary-directory. binary-directory must have a DEBIAN subdirectory, which contains the control information files such as the control file itself." I don't create package with Debian normal method documented, I don't understand how make good package. - Create a debian/rules file. This file is paramount, but it's missing! I insert rules file. I will commit soon. Hope this helps, Aitor. Thanks Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] my first two packages
(...) within each generated packages (...) *package* ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] my first two packages
Hi Viverna, On 17/1/20 23:05, viverna wrote: Hi folks, I tried in my computers a epoch init system homemade package. I have no experience as packager and I don't like bureaucratic style for to make a Debian package or maybe I didn't understand it completely... :-) However I make my first, and maybe last :-) two package: epoch (base program) and epoch-data (config files). Grab it on: https://git.devuan.org/viverna/experimental-epoch https://git.devuan.org/viverna/experimental-epoch-data "make dist" make package "homemade" for arch amd64. Why Epoch? I like init scripts (for example runit) but epoch + daemon configuration file are the simplest infrastructure I know. epoch (program) is a package dependent on epoch-data (config file). Installing epoch, all config files are copied for all daemon installed and if grub is present epoch is added as entry in grub menu. Deleting epoch remove all scripts and entry in grub menu if grub is present. This solution is generic and could be applied for other init system. Init program (base program) and init-data (scripts init/config files). ifj in the devuan infrastructure to inject in all package init freedom (add conf file and init script in all daemon). With collaboration with ifj that disseminates in all packages init scripts or configuration files it could be guaranteed Init Freedom. There is no need of forking all daemon. Create 2 packages (init and init-data) for 1 init system. Create config file/init script for all daemon. Injected with ifj automatically. But there are problems: - I have little time to devote to this project. - Write code is ok for me but I am a very poor packager. I don't understand how make good packages. - I need help for write config file/init script for all daemon. - I (fairly) know only epoch and runit, other init just for the name. - Warning! Use it at your own risk! These packages are very very very experimental! However this could be a first start. My short answer for now: - Use lowercase letters for the debian folder. A DEBIAN folder with uppercase letters will be created within each generated packages. - Create a debian/rules file. This file is paramount, but it's missing! Hope this helps, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] my first two packages
Hi folks,
I tried in my computers a epoch init system homemade package.
I have no experience as packager and I don't like bureaucratic style for
to make a Debian package or maybe I didn't understand it completely...
:-)
However I make my first, and maybe last :-) two package: epoch (base
program) and epoch-data (config files).
Grab it on:
https://git.devuan.org/viverna/experimental-epoch
https://git.devuan.org/viverna/experimental-epoch-data
"make dist" make package "homemade" for arch amd64.
Why Epoch?
I like init scripts (for example runit) but epoch + daemon configuration
file are the simplest infrastructure I know.
epoch (program) is a package dependent on epoch-data (config file).
Installing epoch, all config files are copied for all daemon installed
and if grub is present epoch is added as entry in grub menu. Deleting
epoch remove all scripts and entry in grub menu if grub is present.
This solution is generic and could be applied for other init system.
Init program (base program) and init-data (scripts init/config files).
ifj in the devuan infrastructure to inject in all package init freedom
(add conf file and init script in all daemon).
With collaboration with ifj that disseminates in all packages init
scripts or configuration files it could be guaranteed Init Freedom.
There is no need of forking all daemon.
Create 2 packages (init and init-data) for 1 init system.
Create config file/init script for all daemon.
Injected with ifj automatically.
But there are problems:
- I have little time to devote to this project.
- Write code is ok for me but I am a very poor packager. I don't
understand how make good packages.
- I need help for write config file/init script for all daemon.
- I (fairly) know only epoch and runit, other init just for the name.
- Warning! Use it at your own risk! These packages are very very very
experimental!
However this could be a first start.
--
_
< Viverna >
-
\^/^
\ / \ // \
\ |\___/| / \// .\
\ /0 0 \__ /// | \ \ **
/ / \/_/// | \ \ \ |
@_^_@`/ \/_ //| \ \ \/\ \
//_^_/ \/_ // |\\ \ \
( //) |\/// | \ \ | |
( / /) | // | \ _\ | /
( // /) | ; -.|_ _\.-~ / /
(( / / )) |_ *-.|.-~-. .~~
(( // / ))\ / ~-. _ .-~ /
(( /// )) `. }{ /
(( / )) .~-.\\-` .~
///...<\ _ -~
///-._ _ _ _ _ _ _{^ - - - - ~
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
