[02:40] <dgroos> I've got a question, simple I hope, about using ldap with fat clients.
[02:41] <dgroos> If I make my ltsp server an ldap client to my school districts active directory server...
[02:42] <dgroos> …when a student logs on for the first time to one of my clients (via AD authentication) will it create a home folder for this new user?
[02:43] <dgroos> I'm hoping this because that way I won't have to add new students to the class room ltsp servers.  Since they will have already been added to the school district's AD servers.
[03:16] <dgroos> ok
[03:17] <dgroos> night.
[13:04] <dgroos> Good Morning!
[17:25] <shnatsel> hi everyone
[17:26] <shnatsel> It's just me dreaming or Edubuntu has some kind of system that allows installing only those OS components which the user chooses in ubiquity?
[17:34] <alkisg> shnatsel: you mean something different than the package manager, e.g. synaptic, software center etc?
[17:37] <shnatsel> alkisg: quoting http://edubuntu.org/news/11.04-release : Edubuntu 11.04 ships with a classic Ubuntu desktop by default. Unity is available in both its 2D and 3D versions for these who want to test this new user interface as an option in the installer.
[17:37] <shnatsel> alkisg: quoting http://edubuntu.org/news/11.04-release : Edubuntu 11.04 ships with a classic Ubuntu desktop by default. Unity is available in both its 2D and 3D versions for these who want to test this new user interface as an option in the installer.
[17:38] <shnatsel> sorry dupe
[17:58] <stgraber> shnatsel: yep, I implemented a basic package manager in the graphical installer
[17:58] <alkisg> shnatsel: the desktop environment is a package, yes
[17:58] <stgraber> so you can easily opt-out of some packages and choose to switch between unity and regular gnome
[17:58] <stgraber> LTSP is also an installer option
[17:58] <shnatsel> Awesome!
[17:59] <shnatsel> Are there any docs on configuring this? Ubuntu Studio seems to need this system too.
[18:01] <stgraber> it's nothing too fancy, just an installer component they'd need to ship and change the first few lines so that it shows the right package list
[18:01] <stgraber> might need to split the packages into more meta packages if not already done too and make sure they are Recommends instead of Depends so removing one doesn't remove them all
[18:04] <shnatsel> well, I always follow those rules in elementary, not sure about ubuntu studio guys... but they seem to have enough different metapackages for that.
[18:05] <shnatsel> so, where can I get one and what exactly to change? (btw; why don't you migrate this to dconf or at least config files? changing source code doesn't make sense...)
[18:10] <stgraber> well, changing the source code is usually fine as it's a derivative specifc installer component that's shipped by edubuntu-live, having a configuration file or dconf for that would just make it weird
[18:10] <stgraber> as ubiquity currently doesn't have any configuration
[18:10] <stgraber> and can't use dconf as it can be run in standalone mode
[18:11] <stgraber> the file in question is edubuntu-packages.py in the edubuntu-live package
[18:11] <stgraber> http://paste.ubuntu.com/680779/ is the current content
[18:12] <stgraber> if more official derivatives start using it, I'd probably just move it to ubiquity itself (as I've got commit rights there too)
[18:23] <shnatsel> stgraber: so, to use it in ubuntu studio, the devs will have to customize these lines:
[18:23] <shnatsel>         src_pkg = "edubuntu-meta"
[18:23] <shnatsel>         meta_blacklist = ['edubuntu-server','edubuntu-desktop-kde']
[18:23] <shnatsel>         package_blacklist = ['unity-2d']
[18:23] <shnatsel>         relation_blacklist = ['Depends']
[18:23] <shnatsel> right?
[18:24] <stgraber> yep
[18:24] <shnatsel> ehhh... so, what is what? o_O
[18:24] <stgraber> and also the BEFORE and AFTER flags, quite possibly the translation strings too and import the po template into their package (so they get the installer translated)
[18:31] <shnatsel> so, how do I add or remove packages to/from the list? What do src_pkg, meta_blacklist, package_blacklist and relation_blacklist mean?
[18:33] <stgraber> it's taking src_pkg, looking at the binary packages built from it
[18:34] <stgraber> ignoring these that are in meta_blacklist
[18:34] <stgraber> and then looking for the Depends of each of the remaining meta packages, hiding anything that's listed in package_blacklist
[18:35] <stgraber> and also hiding any package that's a Depend as removing them would remove the whole meta package
[18:56] <shnatsel> stgraber: thanks a lot! I'll try to make a doc out of this convo, I'll drop you a link if I do