Difference between pages "Intel64-nehalem" and "Package:Layman"

(Difference between pages)
 
m
 
Line 1: Line 1:
{{Subarch
+
{{Ebuild
|CPU Family=64-bit Intel Processors
+
|Summary=Tool to manage Gentoo overlays
|subarch=corei7
+
|CatPkg=app-portage/layman
|CHOST=x86_64-pc-linux-gnu
+
|Homepage=http://layman.sourceforge.net/
|CFLAGS=-march=corei7 -O2 -pipe
+
|USE=mmx sse sse2 sse3 ssse3 sse4
+
|Description=The '''corei7''' subarch supports the Nehalem, Westmere, Sandy_Bridge,  Ivy Bridge, and Haswel microarchitecture-based Intel Pentium/Celeron, Intel Core i3, i5, i7 and Xeon Processors.
+
 
}}
 
}}
Beginning in November 2008, Intel launched the first Core i7 processor, codenamed [[Wikipedia:Bloomfield_(microprocessor)|Bloomfield]], based on the [[Wikipedia:Nehalem_(microarchitecture)|Nehalem]] microarchitecture. With this launch, they also added to and modified the conventions used in their [[Wikipedia:Intel_Core|Intel Core]] branding scheme. '''(Not to be confused with the [[Wikipedia:Intel Core (microarchitecture)|Intel Core microarchitecture]]. See [[core2_64]].)'''. This new naming scheme distinguishes between grades of processors rather than microarchitectures or design. Therefore, the '''corei7''' subarch supports the [[Wikipedia:Nehalem_(microarchitecture)|Nehalem]], [[Wikipedia:Westmere_(microarchitecture)|Westmere]], [[Wikipedia:Sandy_Bridge_(microarchitecture)|Sandy Bridge]],  [[Wikipedia:Ivy_Bridge_(microarchitecture)|Ivy Bridge]], and [[Wikipedia:Haswell_(microarchitecture)|Haswell]] microarchitectures under the following brand names:
+
Layman is an "overlay" external repository management tool.
  
* Intel Pentium/Celeron (low-level consumer)
+
=== Installation ===
* Intel Core i3 (entry-level consumer)
+
<console>###i## emerge layman</console>
* Intel Core i5 (mainstream consumer)
+
[[make.conf]] must source laymans overlays for emerge to pull in packages from external sources.  This line needs to be below everything else in make.conf.
* Intel Core i7 (high-end consumer/business)
+
<console>###i## echo "source /var/lib/layman/make.conf" >> /etc/portage/make.conf</console>
* Intel Xeon (business server/workstation)
+
  
See the following links for a list of supported [[Wikipedia:Celeron|Celeron]], [[Wikipedia:Pentium|Pentium]], [[Wikipedia:Intel_Core#Nehalem_microarchitecture_based|Nehalem]], [[Wikipedia:Westmere_(microarchitecture)|Westmere]], [[Wikipedia:Intel_Core#Sandy_Bridge_microarchitecture_based|Sandy Bridge]],  [[Wikipedia:Intel_Core#Ivy_Bridge_microarchitecture_based|Ivy Bridge]], and [[Wikipedia:Intel_Core#Haswell_microarchitecture_based|Haswell]] processors.
+
=== Using Layman ===
 +
Fetch, and display a list of overlays:
 +
<console>###i## layman -L</console>
 +
 
 +
Add an overlay to your system:
 +
<console>###i## layman -a <overlay name></console>
 +
 
 +
Delete an overlay from your system:
 +
<console>###i## layman -d <overlay name></console>
 +
 
 +
==== Masking Overlay Packages ====
 +
Overlays have the power to override distro packages.  To avoid conflicts, mask everything in the overlay, and unmask the packages that are necessary to your system.
 +
 
 +
{{file|name=/etc/portage/package.mask|lang=|desc=mask all packages in an overlay|body=
 +
*/*::overlay-name
 +
}}
 +
 
 +
{{file|name=/etc/portage/package.unmask|lang=|desc=unmask packages to be used|body=
 +
cat-egory/pack-age1
 +
cat-egory/pack-age2
 +
}}
 +
 
 +
==== Sync ====
 +
 
 +
Sync a specific overlays ebuilds:
 +
<console>###i## layman -s <overlay name></console>
 +
 
 +
Sync all overlays:
 +
<console>###i## layman -S</console>
 +
 
 +
Sync all overlays via eix:
 +
<console>###i## eix-sync</console>
 +
 
 +
=== Troubleshooting ===
 +
Problem:
 +
Warning: an installed db file was not found at: ['/var/lib/layman/cache***.xml']
 +
 
 +
Solution:
 +
<console>###i## layman -L</console>
 +
 
 +
{{EbuildFooter}}

Revision as of 12:00, February 3, 2015

app-portage/layman


Source Repository:Repository:Gentoo Portage Tree

http://layman.sourceforge.net/

Summary: Tool to manage Gentoo overlays

Use Flags

bazaar
Support dev-vcs/bzr based overlays
cvs
Support dev-vcs/cvs based overlays
darcs
Support dev-vcs/darcs based overlays
g-sorcery
Support app-portage/g-sorcery based overlays
git
Support dev-vcs/git based overlays
gpg
Support app-crypt/gnupg signed overlays lists and manifests
mercurial
Support dev-vcs/mercurial based overlays
squashfs
Support mounting squashfs image overlays locally read-only
subversion
Support dev-vcs/subversion based overlays
sync-plugin-portage
Install the sys-apps/portage sync module

News

Drobbins

IP Space Migration Continues

All Funtoo user containers in the 8.28 IP space will be moving into our new IP space (172.97) over the next few days. If you have DNS set up -- be sure to watch your container and update to the new IP! container.host.funtoo.org DNS will be updated after the move.
2015-08-27 by Drobbins
Drobbins

Funtoo Hosting IP Move

Funtoo user containers with IPs in the 72.18.x.x range will be gradually migrating to new IP addresses this week. If you have DNS entries for your containers, please be aware that your DNS will need to be updated.
2015-08-11 by Drobbins
Drobbins

New ARM Stages

New ARM Stages, built with a new toolchain, are now hitting mirrors. Existing ARM users should re-install using these stages (dated Aug 3, 2015 or later,) rather than upgrade using emerge.
2015-08-06 by Drobbins
More...

Layman

Tip

We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.

Layman is an "overlay" external repository management tool.

Installation

# emerge layman

make.conf must source laymans overlays for emerge to pull in packages from external sources. This line needs to be below everything else in make.conf.

# echo "source /var/lib/layman/make.conf" >> /etc/portage/make.conf

Using Layman

Fetch, and display a list of overlays:

# layman -L

Add an overlay to your system:

# layman -a <overlay name>

Delete an overlay from your system:

# layman -d <overlay name>

Masking Overlay Packages

Overlays have the power to override distro packages. To avoid conflicts, mask everything in the overlay, and unmask the packages that are necessary to your system.

/etc/portage/package.mask - mask all packages in an overlay
*/*::overlay-name
/etc/portage/package.unmask - unmask packages to be used
cat-egory/pack-age1
cat-egory/pack-age2

Sync

Sync a specific overlays ebuilds:

# layman -s <overlay name>

Sync all overlays:

# layman -S

Sync all overlays via eix:

# eix-sync

Troubleshooting

Problem: Warning: an installed db file was not found at: ['/var/lib/layman/cache***.xml']

Solution:

# layman -L