On Wed, 22 Mar 2006 23:23:25 -0800
Brian <[EMAIL PROTECTED]> wrote:
Will user created lists be located in the /etc/portage directory along
with the other user configs? If so will the format be similar to the
package.* files? For user package lists I imagine there could be the
need to control v
On Thursday 23 March 2006 23:43, Brian wrote:
> On Thu, 2006-23-03 at 22:14 +0900, Jason Stubbs wrote:
> > On Thursday 23 March 2006 16:23, Brian wrote:
> > > /etc/portage/lists/userlist1
> > >
> > > format:
> > >
> > > net-www/apache
> > > www-apache/mod_perl
> > > ...
> >
> > If you make that
On Thu, 2006-23-03 at 22:14 +0900, Jason Stubbs wrote:
> On Thursday 23 March 2006 16:23, Brian wrote:
> > /etc/portage/lists/userlist1
> >
> > format:
> >
> > net-www/apache
> > www-apache/mod_perl
> > ...
>
> If you make that "/etc/portage/sets" and support any package atom (rather
> than onl
On Thursday 23 March 2006 16:23, Brian wrote:
> /etc/portage/lists/userlist1
>
> format:
>
> net-www/apache
> www-apache/mod_perl
> ...
If you make that "/etc/portage/sets" and support any package atom (rather
than only cat/pkg) then I you'd pretty much have what is planned (afaik).
--
Jason S
2006/3/23, Brian <[EMAIL PROTECTED]>:
On Tue, 2006-21-03 at 10:50 -0600, MIkey wrote:> tvali wrote:>> > So, if portage would be looked as lists and operations with lists> > (calculating dependencies of package would be operation with list of
> > that package and list of all - portage tree -, then);
On Tue, 2006-21-03 at 10:50 -0600, MIkey wrote:
> tvali wrote:
>
> > So, if portage would be looked as lists and operations with lists
> > (calculating dependencies of package would be operation with list of
> > that package and list of all - portage tree -, then); building tools
> > [shell comman
On Tue, 21 Mar 2006 10:50:00 -0600
MIkey <[EMAIL PROTECTED]> wrote:
> Add the capability for emerge to take a category as an argument,
# (cd ${PORTDIR_OVERLAY} && emerge -pv /*)
> Then the user can create overlays with their own category names and
> symlink in the package directories they want f
> What about something along these lines...
>
> Add the capability for emerge to take a category as an argument, emerge
> www-apps for example, and emerge all packages within that category.
> Optionally make it so this will only work on categories within
> PORTDIR_OVERLAY, or create a new type of o
tvali wrote:
> So, if portage would be looked as lists and operations with lists
> (calculating dependencies of package would be operation with list of
> that package and list of all - portage tree -, then); building tools
> [shell commands] for creating those lists and tools for operations
> with
