From: fedora-config-list-request@xxxxxxxxxx
Reply-To: fedora-config-list@xxxxxxxxxx
To: fedora-config-list@xxxxxxxxxx
Subject: Fedora-config-list Digest, Vol 16, Issue 5
Date: Fri, 10 Jun 2005 12:00:10 -0400 (EDT)
Send Fedora-config-list mailing list submissions to
fedora-config-list@xxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://www.redhat.com/mailman/listinfo/fedora-config-list
or, via email, send a message with subject or body 'help' to
fedora-config-list-request@xxxxxxxxxx
You can reach the person managing the list at
fedora-config-list-owner@xxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Fedora-config-list digest..."
Today's Topics:
1. pup use cases... (Chris McDonough)
2. Re: pup use cases... (Matthew Miller)
3. Re: pup use cases... (Paul Nasrat)
4. Re: pup use cases... (Chris McDonough)
5. Re: pup use cases... (Chris McDonough)
6. Re: pup use cases... (Matthew Miller)
----------------------------------------------------------------------
Message: 1
Date: Thu, 09 Jun 2005 14:45:56 -0400
From: Chris McDonough <chrism@xxxxxxxxx>
Subject: pup use cases...
To: fedora-config-list@xxxxxxxxxx
Message-ID: <1118342756.24600.7.camel@xxxxxxxxxxxxxxxx>
Content-Type: text/plain
Hi all,
I'm taking a look at the ""pup storyboard" from a checkout of Paul
Nasrat's pup package.
The storyboard seems to indicate that the most compelling use case is
the one currently fulfilled by up2date/rhn-applet, where a user is
notified that an update is available for software that he or she already
has installed, and allows them to install the updates in a 'batch'.
I am wondering if anyone has an idea of whether it's within pup's
current presumed scope to also allow users to manage the process of
graphically adding new software and removing installed software on an
ad-hoc basis (e.g. Synaptic).
Any pointers to existing conversations about this are welcome too.
- C
------------------------------
Message: 2
Date: Thu, 9 Jun 2005 15:14:26 -0400
From: Matthew Miller <mattdm@xxxxxxxxxx>
Subject: Re: pup use cases...
To: Discussions about configuration tool development
<fedora-config-list@xxxxxxxxxx>
Message-ID: <20050609191426.GA19662@xxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii
On Thu, Jun 09, 2005 at 02:45:56PM -0400, Chris McDonough wrote:
> I am wondering if anyone has an idea of whether it's within pup's
> current presumed scope to also allow users to manage the process of
> graphically adding new software and removing installed software on an
> ad-hoc basis (e.g. Synaptic).
As I understand it, it's very much not.
--
Matthew Miller mattdm@xxxxxxxxxx <http://www.mattdm.org/>
Boston University Linux ------> <http://linux.bu.edu/>
Current office temperature: 81 degrees Fahrenheit.
------------------------------
Message: 3
Date: Thu, 09 Jun 2005 15:27:20 -0400
From: Paul Nasrat <pnasrat@xxxxxxxxxx>
Subject: Re: pup use cases...
To: Discussions about configuration tool development
<fedora-config-list@xxxxxxxxxx>
Message-ID: <1118345240.3288.14.camel@xxxxxxxxxx>
Content-Type: text/plain
On Thu, 2005-06-09 at 14:45 -0400, Chris McDonough wrote:
> Hi all,
>
> I'm taking a look at the ""pup storyboard" from a checkout of Paul
> Nasrat's pup package.
Cool. If you want to test it out you can
cd data; sudo python mockpup.py
I'll move to having a real binary later this week - along with makefiles
and spec for test releases.
> The storyboard seems to indicate that the most compelling use case is
> the one currently fulfilled by up2date/rhn-applet, where a user is
> notified that an update is available for software that he or she already
> has installed, and allows them to install the updates in a 'batch'.
Yes that is correct.
> I am wondering if anyone has an idea of whether it's within pup's
> current presumed scope to also allow users to manage the process of
> graphically adding new software and removing installed software on an
> ad-hoc basis (e.g. Synaptic).
Not with pup itself. The aim is to have a complete graphical suite for
software management using yum as the backend from anaconda installation,
package updates and software installation.
pup is focused on the package update component. We may endup with
reusable parts such as progress bars and callbacks, but the installation
interface is distinct from updates.
Paul
------------------------------
Message: 4
Date: Thu, 09 Jun 2005 19:41:40 -0400
From: Chris McDonough <chrism@xxxxxxxxx>
Subject: Re: pup use cases...
To: Discussions about configuration tool development
<fedora-config-list@xxxxxxxxxx>
Message-ID: <1118360500.7471.3.camel@xxxxxxxxxxxxxxxx>
Content-Type: text/plain
On Thu, 2005-06-09 at 15:14 -0400, Matthew Miller wrote:
> On Thu, Jun 09, 2005 at 02:45:56PM -0400, Chris McDonough wrote:
> > I am wondering if anyone has an idea of whether it's within pup's
> > current presumed scope to also allow users to manage the process of
> > graphically adding new software and removing installed software on an
> > ad-hoc basis (e.g. Synaptic).
>
> As I understand it, it's very much not.
I see... thanks! I was going to try to contribute, but I'm not sure
what the benefit is of replacing the existing utilities that already do
that.
- C
------------------------------
Message: 5
Date: Thu, 09 Jun 2005 19:54:49 -0400
From: Chris McDonough <chrism@xxxxxxxxx>
Subject: Re: pup use cases...
To: Discussions about configuration tool development
<fedora-config-list@xxxxxxxxxx>
Message-ID: <1118361289.7471.6.camel@xxxxxxxxxxxxxxxx>
Content-Type: text/plain
On Thu, 2005-06-09 at 15:27 -0400, Paul Nasrat wrote:
> On Thu, 2005-06-09 at 14:45 -0400, Chris McDonough wrote:
> > Hi all,
> >
> > I'm taking a look at the ""pup storyboard" from a checkout of Paul
> > Nasrat's pup package.
>
> Cool. If you want to test it out you can
>
> cd data; sudo python mockpup.py
Yep, tried it, looks good! ;-)
> > I am wondering if anyone has an idea of whether it's within pup's
> > current presumed scope to also allow users to manage the process of
> > graphically adding new software and removing installed software on an
> > ad-hoc basis (e.g. Synaptic).
>
> Not with pup itself. The aim is to have a complete graphical suite for
> software management using yum as the backend from anaconda installation,
> package updates and software installation.
>
> pup is focused on the package update component. We may endup with
> reusable parts such as progress bars and callbacks, but the installation
> interface is distinct from updates.
Gotcha... that helps a lot, thanks. I'm hot for an ad-hoc installation
tool, but maybe I should start playing around with pup first given that
it's the first in the series of things that aim to get done. I gather
that the combination of up2date and rhn-applet-gui is pretty crufty, and
that's why we need pup?
- C
------------------------------
Message: 6
Date: Thu, 9 Jun 2005 20:57:19 -0400
From: Matthew Miller <mattdm@xxxxxxxxxx>
Subject: Re: pup use cases...
To: Discussions about configuration tool development
<fedora-config-list@xxxxxxxxxx>
Message-ID: <20050610005719.GA32168@xxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii
On Thu, Jun 09, 2005 at 07:41:40PM -0400, Chris McDonough wrote:
> I see... thanks! I was going to try to contribute, but I'm not sure
> what the benefit is of replacing the existing utilities that already do
> that.
You may want to see if Tim Lauridsen, the developer of yumex
<http://fedoranews.org/tchung/yumex/> would like some help....
--
Matthew Miller mattdm@xxxxxxxxxx <http://www.mattdm.org/>
Boston University Linux ------> <http://linux.bu.edu/>
Current office temperature: 81 degrees Fahrenheit.
------------------------------
--
Fedora-config-list mailing list
Fedora-config-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-config-list
End of Fedora-config-list Digest, Vol 16, Issue 5
*************************************************
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
--
Fedora-config-list mailing list
Fedora-config-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-config-list