[gentoo-dev] Web Portage

[gentoo-dev] Web Portage

[Troy Dack]

I posted a little while ago about making a web interface to portage.

Well after a bit of hacking, a great deal of reading and even more
reading (including an O'Rielly Safari subscription) I present you with
the (small) fruits of my labours:

	http://sourceforge.net/projects/webportage

or for those wanting to jump in at the deep end:

http://sourceforge.net/project/showfiles.php?group_id=67364&release_id=12570

Try it out and let me what know you think (be nice).

The package has a dependency on a 3rd party python module.  An ebuild is
included.  For those fluent in python I'm sure you can work out what to
remove to get around the issue.

Oh, and if you do take the time to get it working, attempting to do an
actual emerge will result in failure -- it's a work in progress.

Thanks

-- 
	Troy Dack
	http://linux.tkdack.com


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Web Portage

[Tom Prado]

This looks very nice!  I like the color highlights for ebuilds that have 
been installed and those that are masked.  Here's a few things that you 
may want to consider:

1)  This is most likely already in your plans:  an emerge rsync button 
and an emerge -u system button.  Maybe even an emerge --clean button.

2)  The ability to set the ACCEPT_KEYWORDS when merging.  Perhaps even 
cache these settings somehow.

3)  The ability to do the stages of ebuild directly, i.e. ebuild 
<file.ebuild> unpack, compile, install, merge.

4)  The ability to merge previous versions of an ebuild.


That's the only suggestions I can come up with at the moment.   Keep up 
the good work!


Tom Prado


Troy Dack wrote:
> I posted a little while ago about making a web interface to portage.
> 
> Well after a bit of hacking, a great deal of reading and even more
> reading (including an O'Rielly Safari subscription) I present you with
> the (small) fruits of my labours:
> 
> 	http://sourceforge.net/projects/webportage
> 
> or for those wanting to jump in at the deep end:
> 
> http://sourceforge.net/project/showfiles.php?group_id=67364&release_id=12570
> 
> Try it out and let me what know you think (be nice).
> 
> The package has a dependency on a 3rd party python module.  An ebuild is
> included.  For those fluent in python I'm sure you can work out what to
> remove to get around the issue.
> 
> Oh, and if you do take the time to get it working, attempting to do an
> actual emerge will result in failure -- it's a work in progress.
> 
> Thanks
>  




--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Web Portage

[Troy Dack]

Tom,
	Thanks for the feed back.

On Wed, 2002-12-04 at 14:56, Tom Prado wrote:
> 
> This looks very nice!  I like the color highlights for ebuilds that have 
> been installed and those that are masked.  Here's a few things that you 
> may want to consider:
> 
> 1)  This is most likely already in your plans:  an emerge rsync button 
> and an emerge -u system button.  Maybe even an emerge --clean button.

Yep, I'm still working out CVS and SourceForge, I have a TODO list
around somewhere and that is one of the things on it
 
> 2)  The ability to set the ACCEPT_KEYWORDS when merging.  Perhaps even 
> cache these settings somehow.

I'm leaning towards a sort of "config" page so you can set
ACCEPT_KEYWORDS and PORTDIR_OVERLAY on the fly.  I've already got
rudimentary config file settings (/etc/webportage.conf) and I'm thinking
of saving these sort of things in here.

I don't want to duplicate any config options that Portage already uses
though ... having to set the same env vars in two places for essentially
the same purpose is not a good idea :)

> 3)  The ability to do the stages of ebuild directly, i.e. ebuild 
> <file.ebuild> unpack, compile, install, merge.

OK, I'll see what I can do.

> 4)  The ability to merge previous versions of an ebuild.

I've been thinking about this one too, the only problem is that old
ebuilds will be periodically wiped because emerge rsync now does a clean
by default to remove old ebuilds.  I think this action was taken because
some people were using known broken ebuilds and still reporting the
errors in bugzilla.

I'll look into it though.
 
> 
> That's the only suggestions I can come up with at the moment.   Keep up 
> the good work!
> 
> 
> Tom Prado

Thanks for taking the time to give it a try, it means a lot :)

-- 
	Troy Dack
	http://linux.tkdack.com


--
gentoo-dev@gentoo.org mailing list