Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 3DF1FE00D2C; Mon, 4 Mar 2019 22:01:32 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at https://www.dnswl.org/, * medium trust * [147.11.1.11 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id D2C34E00D28 for ; Mon, 4 Mar 2019 22:01:31 -0800 (PST) Received: from ALA-HCA.corp.ad.wrs.com ([147.11.189.40]) by mail.windriver.com (8.15.2/8.15.1) with ESMTPS id x2561Ttr021661 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 4 Mar 2019 22:01:29 -0800 (PST) Received: from [128.224.163.141] (128.224.163.141) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.3.439.0; Mon, 4 Mar 2019 22:01:28 -0800 To: , "yocto@yoctoproject.org" From: ChenQi Message-ID: <6323ed1d-0e39-4d07-e691-5e3e07f007f9@windriver.com> Date: Tue, 5 Mar 2019 14:11:13 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 X-Originating-IP: [128.224.163.141] Subject: [opkg-utils] Question: why update-alternatives from opkg-utils chooses /usr/lib to hold database? X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Mar 2019 06:01:32 -0000 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Hi All, Recently I'm dealing with issue from which some discussion raises. I'd like to ask why update-alternatives from opkg-utils chooses /usr/lib to hold its alternatives database? I looked into debian, its update-alternatives chooses /var/lib by default. Is there some design consideration? Or some historical reason? Best Regards, Chen Qi