All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ran Shalit <ranshalit@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: apt-get
Date: Fri, 10 Nov 2017 10:06:20 +0200	[thread overview]
Message-ID: <CAJ2oMhLej=EWrQCjXkywWOO0jtuWeKZmVXPU5cW_+qcJ7go3YQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ2oMhLuRMSvyZkjcdek6AUVHLw81semMer1+=nmZPQ8eQOP0w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4097 bytes --]

If I can please ask one last on this issue:

We decided to try "smart", but it seems that its mirrors list are all
empty.
Can you please point me as to how to fill the mirror list (I tried to
search on this, but haven't found information) ?

Thank you very much,
Ran



On Thu, Nov 9, 2017 at 5:11 PM, Ran Shalit <ranshalit@gmail.com> wrote:

> I now see that I have smart:
> root@lec-imx6:~# smart
> Usage: smart command [options] [arguments]
>
> I was not familiar with "smart" command before, so that is good enough.
>
> The image is based on fsl-image-qt5 image  (lec-imx6 from adlink)
>
> Thanks,
> Ran
>
> On Thu, Nov 9, 2017 at 5:01 PM, Burton, Ross <ross.burton@intel.com>
> wrote:
> > What release?  Until recently we used smart not yum.
> >
> > Ross
> >
> > On 9 November 2017 at 14:56, Ran Shalit <ranshalit@gmail.com> wrote:
> >>
> >> I've added in local.conf both:
> >> PACKAGE_CLASSES = "package_rpm"
> >> IMAGE_FEATURES += "package-management"
> >>
> >> Yet, I don't have yum command, only rpm command.
> >>
> >> Regards,
> >> Ran
> >>
> >> On Thu, Nov 9, 2017 at 1:25 PM, Burton, Ross <ross.burton@intel.com>
> >> wrote:
> >> > (adding yocto@ back to CC)
> >> >
> >> > I don't know where you saw that but that is very wrong.
> >> >
> >> > Set PACKAGE_CLASSES to the package manager that you want to use.  If
> you
> >> > want to use opkg, then PACKAGE_CLASSES should be package_ipk
> (historical
> >> > naming).  If you want opkg to be present in the images ensure
> >> > IMAGE_FEATURES
> >> > contains package-management.
> >> >
> >> > PACKAGE_CLASSES controls what package formats are generated, and
> >> > multiple
> >> > are supported for flexibility and testing purposes.  For real world
> use
> >> > there's no need to have more than one.  The first entry is the package
> >> > type
> >> > that is actually used in the rootfs generation.
> >> >
> >> > package-management needs to be in IMAGE_FEATURES to both get the tools
> >> > installed (opkg in your case, apt-get for dpkg, yum for rpm) and to
> keep
> >> > the
> >> > package management database on the disk.  By removing
> package-management
> >> > from IMAGE_FEATURES all traces of the package manager will be removed
> >> > from
> >> > the rootfs, which is useful if you don't want to support on-target use
> >> > of
> >> > the package manager.
> >> >
> >> > Ross
> >> >
> >> > On 9 November 2017 at 06:45, Ran Shalit <ranshalit@gmail.com> wrote:
> >> >>
> >> >> Hi,
> >> >>
> >> >> We also consider using opkg.
> >> >>
> >> >> Now, I have some confusion as to how to install opkg.
> >> >> I see in some documentation that it should be installed as following:
> >> >>
> >> >> PACKAGE_CLASSES ?= "package_rpm package_ipk"
> >> >> IMAGE_INSTALL_append = " opkg "
> >> >>
> >> >> Does it mean there are 2 package managers active ?
> >> >> How can we know which of them is active ?
> >> >>
> >> >>
> >> >> If "?=" means that it shall be defined only if not defined
> previously,
> >> >> so if it is already defined as  package_rpm , it might not install
> >> >> package_ipk?
> >> >> Doesn't it mean that "opkg" might be installed without the required
> >> >> package_ipk ?
> >> >>
> >> >> Thank you,
> >> >> Ran
> >> >>
> >> >> On Wed, Nov 8, 2017 at 9:26 PM, Burton, Ross <ross.burton@intel.com>
> >> >> wrote:
> >> >> > Set PACKAGE_CLASSES to package_deb, and then ensure IMAGE_FEATURES
> >> >> > includes
> >> >> > package-management.
> >> >> >
> >> >> > Ross
> >> >> >
> >> >> > On 8 November 2017 at 19:16, Ran Shalit <ranshalit@gmail.com>
> wrote:
> >> >> >>
> >> >> >> Hello,
> >> >> >>
> >> >> >> Is there a way to add "apt-get" command (and package manager) in
> >> >> >> yocto
> >> >> >> ?
> >> >> >>
> >> >> >> Thank you,
> >> >> >> Ran
> >> >> >> --
> >> >> >> _______________________________________________
> >> >> >> yocto mailing list
> >> >> >> yocto@yoctoproject.org
> >> >> >> https://lists.yoctoproject.org/listinfo/yocto
> >> >> >
> >> >> >
> >> >
> >> >
> >
> >
>

[-- Attachment #2: Type: text/html, Size: 6384 bytes --]

  reply	other threads:[~2017-11-10  8:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 19:16 apt-get Ran Shalit
2017-11-08 19:26 ` apt-get Burton, Ross
     [not found]   ` <CAJ2oMhKQ=R615oVu2i-_verahERksqhMtxKq0RkjcxCmXnbKkQ@mail.gmail.com>
2017-11-09 11:25     ` apt-get Burton, Ross
2017-11-09 14:56       ` apt-get Ran Shalit
2017-11-09 15:01         ` apt-get Burton, Ross
2017-11-09 15:11           ` apt-get Ran Shalit
2017-11-10  8:06             ` Ran Shalit [this message]
2017-11-10 10:50         ` apt-get Zoran Stojsavljevic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ2oMhLej=EWrQCjXkywWOO0jtuWeKZmVXPU5cW_+qcJ7go3YQ@mail.gmail.com' \
    --to=ranshalit@gmail.com \
    --cc=ross.burton@intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.