<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">debname:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> The text is unclear.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> I think you are saying that the deb
built out of directory "integ/base/dhcp" would get the name "dhcp"
by defult. However the Debian convention is to call this package
"isc-dhcp" so we must include a "integ/base/dhcp/debian/debname"
file to force the package we build to receive the name "isc-dhcp"</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">deb_folder:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> This overrides the upstream folder
entirely? It can't be used to add files or override specific
upstream files? If it does override the entire folder, perhaps we
need a warning from the package builder that the override has
occurred.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">src_path:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> Should support some common macros
rather than relying strictly on relative paths. This aids in code
restructuring, both within and across gits.</div>
<div class="moz-cite-prefix"> e.g. we have macros like...
PKG_BASE, GIT_BASE, STX_BASE<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">general:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> At some point it would be desirable
to have a tool to aid in patch creation. It should use git.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> Currently build-pkg --edit tries to
do this, but it's not very reliable as rpm's approach to patching
fairly free-form and hard to automate.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> e.g. stx edit --pkg-type=debian
--package=dhcp</div>
<div class="moz-cite-prefix"> = it copies 'debian' to a working
directory and does git init, git add --all, git commit<br>
</div>
<div class="moz-cite-prefix"> = It copies tarball source into a
second working directory and does git init, git add --all, git
commit</div>
<div class="moz-cite-prefix"> = It applies 'patches' and
'deb_patches' to the correct gits, in the correct order, and
creates a git commit for each.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> The user can then edit files,
cherry-pick a fix from elsewhere, re-order or delete a patch...
etc.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> Finally the user uses git
format-patch to regenerate the patch and deb-patch series ... or
perhaps this step is covered by the 'stx' tool ...</div>
<div class="moz-cite-prefix"> stx edit --publish
--pkg-type=debian --package=dhcp</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> One major use of tis is to 'de-fuzz'
patches when moving to a new upstream version/tarball<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2021-07-26 3:33 a.m., ytao wrote:<br>
</div>
<blockquote type="cite" cite="mid:ee454e12-917b-ef3f-bc12-f4eb3b24f480@windriver.com">Hello
Everyone:
<br>
<br>
You may have known Wind River team is working on the transition to
Debian OS, more details of the project can be found at
<a class="moz-txt-link-freetext" href="https://docs.starlingx.io/specs/specs/stx-6.0/">https://docs.starlingx.io/specs/specs/stx-6.0/</a>. My purpose is
launching a discussion about the userspace packages transition to
Debian. The spec can be found at
<a class="moz-txt-link-freetext" href="https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_2008704_debian_transition.html">https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_2008704_debian_transition.html</a><br>
<br>
In order to inherit the existing userspace construction as much as
possible, our proposal is creating a 'debian' folder in same
directory with 'centos' folder for each package. For example, the
dhcp package in integ repo, it's centos folder is at:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://opendev.org/starlingx/integ/src/branch/master/base/dhcp/centos">https://opendev.org/starlingx/integ/src/branch/master/base/dhcp/centos</a>
<br>
<br>
We will create a debian folder in same location
<br>
<br>
<a class="moz-txt-link-freetext" href="https://opendev.org/starlingx/integ/src/branch/master/base/dhcp/debian">https://opendev.org/starlingx/integ/src/branch/master/base/dhcp/debian</a>.
<br>
<br>
All materials in this folder control building dhcp under Debian
host. The "stx_deb_folder_layout.rst" is the layout of debian
folder. I also attach a couple of samples to demonstrate how to
fill the debian folder for a debian package and a 3rd package.
<br>
<br>
This layout is not the final version, I'm appreciated for any
suggestion from you.
<br>
<br>
<br>
Thanks,
<br>
<br>
ytao
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Starlingx-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Starlingx-discuss@lists.starlingx.io">Starlingx-discuss@lists.starlingx.io</a>
<a class="moz-txt-link-freetext" href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>