A maintained package.use file

Anything that pertains to Portage

Moderator: Moderators

A maintained package.use file

Postby pirieianip » Fri Feb 17, 2012 4:32

The idea is:

A "/etc/portage/package.used" file that has a linked package on your end with all the flags that sabayon uses in its packages for the end product. Whenever you refresh portage, it refreshes that file. If there is declared package that you are installing in the "/etc/portage/package.use", it will take over its responsibility or trump the "package.used" file. This way you are basically mainstreaming how to use portage for those who don't know how to. Also, it should update the package.mask and all the other fun stuff that you use like etc-update. That way if you want to easily update your system in the compilation method and reap the slight benefit, you've got it without worrying. I just suggest alternate files for it that are trumped by the user file... for instance, the "package.use" file is the user file, the "package.used" file is the file that has the default use commands. For portage...

Counter arguements/ arguements.... Go! :lol: :pirat: :alien:
pirieianip
Baby Hen
 
Posts: 16
Joined: Sun Feb 12, 2012 23:07
Location: Ohio

Re: A maintained package.use file

Postby Thev00d00 » Fri Feb 17, 2012 16:25

Image
Please report Bugs on the Bugzilla, not forum
Please Adopt an Unanswered thread
Website / Blog : v00d00.net
twitter: Follow Me
G+: Circle Me
User avatar
Thev00d00
Generally Awesome (tm)
 
Posts: 1467
Joined: Wed Feb 21, 2007 15:52
Location: United Kingdom

Re: A maintained package.use file

Postby pirieianip » Fri Feb 17, 2012 17:20

I am not entirely certain but it seems like it is missing a few packages on it. I mean for all the packages as well. I also think this way, you can help end users in case they do a emerge world or install and it isn't on that list/ has been updated to include different use commands.

I also would like to see that in the make.conf in the install package for gcc, the march command be changed to native from I think either blank or i686. I know this is a little thing but I think it is a good implementation. Entropy is good and all, just I would like to see some additional improvements for portage.

I would try to help more in development/bug issues if I could alas, your system isn't supported to my knowledge by my wireless card because I really like the work you all have done. I have your system on a VM as we speak and I would like to change to this OS as it seems like a) it seems more like you CAN do anything you want with it in configuration, b) it is less corporately controlled, and c) your forums aren't a sprawling mass thathas too many facets places to search( need one bar for the entire database) wonder who I am talking about...
pirieianip
Baby Hen
 
Posts: 16
Joined: Sun Feb 12, 2012 23:07
Location: Ohio

Re: A maintained package.use file

Postby pirieianip » Fri Feb 17, 2012 17:51

That being said, I am still a newbie when it comes to OS creation though I would like to learn more. Any suggestions to read?
pirieianip
Baby Hen
 
Posts: 16
Joined: Sun Feb 12, 2012 23:07
Location: Ohio


Return to Portage|Emerge Package Managers

Who is online

Users browsing this forum: No registered users and 2 guests