[jhalfs] branch trunk updated: BLFS: remove only "a" lines for runtime deps

"Git Owner" ([email protected] via alfs-discuss Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.automated
Message-ID <166255909688.8815.13933058023894784218@rivendell.linuxfromscratch.org>
This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch trunk
in repository jhalfs.

The following commit(s) were added to refs/heads/trunk by this push:
     new 5156f51  BLFS: remove only "a" lines for runtime deps
5156f51 is described below

commit 5156f518599b40cd1febae71614c346ff825b1d0
Author: Pierre Labastie <[email protected]>
AuthorDate: Wed Sep 7 15:51:45 2022 +0200

    BLFS: remove only "a" lines for runtime deps
    
    Presently, when the <node>groupxx file is created, we copy "a"
    lines from <node> to <node>groupxx (changing "a" to "b") and
    we remove all the lines containing the runtime dependency from
    <node>. This may not always be what we want: for example, a
    dependency can be both "required at runtime" and "optional for
    tests". We should keep this information when cleaning the nodes.
    Only when removing circular paths should the optional tie be broken
    if necessary.
---
 BLFS/libs/func_dependencies | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/BLFS/libs/func_dependencies b/BLFS/libs/func_dependencies
index 492659c..8c05a88 100644
--- a/BLFS/libs/func_dependencies
+++ b/BLFS/libs/func_dependencies
@@ -399,7 +399,7 @@ for node in $(grep -l ' a ' *.dep); do
   done
   } <$node
   for id_of_dep in $lines_to_remove; do
-    sed "/\ $id_of_dep\$/d" -i $node
+    sed "/a\ $id_of_dep\$/d" -i $node
   done
 done
 for node in $(grep -l ' f ' *); do

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.

-- 
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.