All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Prasant J <pj0585@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Embedded Linux Package Management
Date: Fri, 20 Mar 2015 11:26:43 +0100	[thread overview]
Message-ID: <550BF5E3.90900@dynamicdevices.co.uk> (raw)
In-Reply-To: <CAA2DH4sioAGo95HRzHGyiYGHiDunUhStFM8v9KsqPUQJznRMcg@mail.gmail.com>



On 20/03/2015 11:15, Prasant J wrote:
> On Fri, Mar 20, 2015 at 2:21 PM, Alex J Lennon
> <ajlennon@dynamicdevices.co.uk> wrote:
>>
>> On 20/03/2015 09:34, Prasant J wrote:
>>
>> Hi,
>>
>> I'm looking for package management for my embedded linux systems
>> (yocto on armv7 iMX6Q)
>>
>>
>> I'm looking for the following features:
>>
>> (a) Install & remove a package
>> (b) Install packages and its dependencies
>> (c) Install a package with conflicts, such that the conflicting
>> package is force removed
>> (d) A local location with packages should serve as a package source
>> (e) Remote server package (http file server based)
>> (f) List of my packages installed
>> (g) List of my packages not installed but available on the http file server
>> (h) List of my packages that have updates (new version)
>> (i) To be able to manage packages for multiple architectures (eg. rpm
>> can produce packages for multiple architectures using one spec file)
>>
>>
>> The above features will be invoked by the application GUI.
>> Any suggestions: which package management solution would answer all
>> the above use cases?
>>
>>
>>
>> (e) I use smart + RPM. I have a remote package server setup via this in
>> local.conf
>>
>> FEED_DEPLOYDIR_BASE_URI = "http://packages.foo.bar"
>>
>> Then I'm rsyncing the files up to the server after a bitbake package-index.
>>
>> Then smart update / search / install
>>
>> That seems to work well in my testing.
>>
>
> Hi Alex,
>
> Thanks for inputs!
>
> Is smart development stopped?
>
> When I look at their mailing list it, the last posts were in Nov 2014.
> It looks like no more development for smart package manager. I would
> then tend to say that it will not be a right way for me.
>

I don't know. To me the question would be does it do want I need it to
do as well as I need it to do it,
rather than asking whether there is a lot of activity. One might take
the view that if it is doing its job,
a lack of activity is a sign that it's a mature piece of software that
needs little further development.

You'll have to make that decision yourself.

My understanding is that smart is the recommended way to do things (at
least it was what was
recommended to me) - https://wiki.yoctoproject.org/wiki/Smart

Regards, Alex
 


  reply	other threads:[~2015-03-20 10:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20  8:34 Embedded Linux Package Management Prasant J
2015-03-20  8:51 ` Alex J Lennon
2015-03-20 10:15   ` Prasant J
2015-03-20 10:26     ` Alex J Lennon [this message]
2015-03-20 11:10       ` Paul Eggleton
2015-03-20 11:14         ` Paul Eggleton
2015-03-21  8:40           ` Prasant J
2015-03-24 16:19             ` Mark Hatle
2015-03-24 19:05           ` Benjamin Esquivel

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=550BF5E3.90900@dynamicdevices.co.uk \
    --to=ajlennon@dynamicdevices.co.uk \
    --cc=pj0585@gmail.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.