Difference between pages "LXQt" and "Package:Layman"

(Difference between pages)
(fix)
 
 
Line 1: Line 1:
== About LXQt ==
+
{{Ebuild
 +
|Summary=Tool to manage Gentoo overlays
 +
|CatPkg=app-portage/layman
 +
|Homepage=http://layman.sourceforge.net/
 +
}}
 +
Layman is an "overlay" external repository management tool.
  
LXQt is a lightweight Desktop environment. Some LXDE developers decided to create a Qt based version of their Desktop environment, it's name was lxde-qt. Around the same time some other people were working on a different minimal Qt based DE called razor-qt. When some developers of those projects met they decided to join forces and work together on one project. LXQt was born.
+
=== Installation ===
 +
<console>###i## emerge layman</console>
 +
=== Using Layman ===
 +
Fetch, and display a list of overlays:
 +
<console>###i## layman -L</console>
  
== Installation ==
+
Add an overlay to your system:
 +
<console>###i## layman -a <overlay name></console>
 +
After adding first overlay(s) [[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.
 +
<console>###i## echo "source /var/lib/layman/make.conf" >> /etc/portage/make.conf</console>
 +
Delete an overlay from your system:
 +
<console>###i## layman -d <overlay name></console>
  
It is recommended to set the LXQt mix-in before emerging it.
+
==== 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.
  
{{console|body=
+
{{file|name=/etc/portage/package.mask|lang=|desc=mask all packages in an overlay|body=
###i## eselect profile add funtoo/1.0/linux-gnu/mix-ins/lxqt
+
*/*::overlay-name
###i## emerge lxqt-meta
+
 
}}
 
}}
  
== Starting LXQt ==
+
{{file|name=/etc/portage/package.unmask|lang=|desc=unmask packages to be used|body=
 +
cat-egory/pack-age1
 +
cat-egory/pack-age2
 +
}}
  
You can either use a display manager to log into your system and start LXQt, or you can log in on a TTY and run {{c|startx}} to start xinit by hand.
+
==== Sync ====
  
=== xinit ===
+
Sync a specific overlays ebuilds:
 +
<console>###i## layman -s <overlay name></console>
  
You should edit the file  {{c|~/.xinitrc}} if it already exists, and put {{c|"exec startlxqt"}} in there.
+
Sync all overlays:
If it doesn't exist you can create it like this:
+
<console>###i## layman -S</console>
 
+
{{console|body=$##i## echo "exec startlxqt" > ~/.xinitrc}}
+
 
+
You might want to add the commands and options {{c|ck-launch-session dbus-launch --sh-syntax --exit-with-session}} to the {{c|exec]}} to start it with ConsoleKit and DBus.
+
In this case you also need to add ConsoleKit to the default runlevel:
+
 
+
{{console|body=
+
###i## rc-update add consolekit default
+
###i## rc
+
}}
+
  
 +
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']
  
=== Login Manager ===
+
Solution:
 +
<console>###i## layman -L</console>
  
Please take a look at http://www.funtoo.org/Package:XDM_%28Display_Manager%29 for this.
+
{{EbuildFooter}}

Latest revision as of 08:20, February 13, 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

Using Layman

Fetch, and display a list of overlays:

# layman -L

Add an overlay to your system:

# layman -a <overlay name>

After adding first overlay(s) 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

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