John,<br><br> I see now. I agree, man-power is better spent on things other than separating the free-cell game from the games package. I was simply trying to figure out the reason why, and see if there was some way I could contribute to giving the users of Ubuntu more freedom on what they have on their system.<br>
<br> Thanks for clearing that up for me.<br>-Mike<br><br><div class="gmail_quote">On Mon, Mar 23, 2009 at 12:30 PM, John Carr <span dir="ltr"><<a href="mailto:john.carr@unrouted.co.uk">john.carr@unrouted.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2009/3/23 Mike Jones <<a href="mailto:eternalorb@gmail.com">eternalorb@gmail.com</a>>:<br>
<div><div></div><div class="h5">> Hi guys. Thanks for your detailed replies.<br>
><br>
> I think I'm having a difficult time expressing what I'm trying to get<br>
> across. It's kind of a vague notion.<br>
><br>
> My problem isn't that for me its difficult to either just remove the<br>
> package entirely (in this case, I don't play any of those games and don't<br>
> see a situation where I will want to for the foreseeable future. If it<br>
> decide I want to, I will simply install the package again.) I understand<br>
> that I can go to the terminal and remove or modify the portions of the<br>
> system I want to manually. (I recommend that you not suggest that to anyone<br>
> in the future. 60% of my time using Ubuntu is in a terminal, and I am more<br>
> than aware that mucking around in the system is a *bad* idea. I don't know<br>
> what files to modify in what order, and I doubt that it would be easy to<br>
> find the information within 5 minutes).<br>
><br>
> The problem isn't that the space required for these packages is<br>
> bothersome. I'm fortunate enough to have relatively new hardware and plenty<br>
> of storage. The space needed for those extra games is effectively trivial<br>
> for me.<br>
><br>
> In terms of repackaging the programs: I am more than appreciative of<br>
> those who spend their time packaging programs for Ubuntu. Even those who<br>
> package programs I don't use are appreciated. You're right. It would be<br>
> futile for me to repackage the collection of programs for my own personal<br>
> use. That would be silly.<br>
><br>
> So I wanted to emphasise that I'm not a nieve user. I am a Software<br>
> Engineering student, and spend a large amount of time doing software<br>
> development at my job. I know a decent approximation of how the various<br>
> components that I concern myself with work. Well enough to know what I need<br>
> to look up, anyway.<br>
><br>
> I think I really wanted to get across was "Whats keeping<br>
> apt/aptitude/gdebi/synaptic/add-remove/ what-have-you from being able to<br>
> cherry pick components of a package? Is there some hard and fast technical<br>
> limitation? Would anyone like to offer suggestions to me for where I can<br>
> look into improving the system? Is it feasable to do so?" Any time my tools<br>
> (In this case add-remove, or the other front-ends for the package manager)<br>
> tell me I can't do something I know I should be able to do, I'm bothered. A<br>
> non-advanced user is going to see that message reply and say "Well why the<br>
> hell can't I remove one of them? Just delete it!" I know they will. I heard<br>
> my brother screaming that the other day when he couldn't remove who knows<br>
> what. It is non-intuitive to not be able to remove or add single programs,<br>
> and instead be told to install entire packages. I understand the realistic<br>
> reasons why this is so, but it doesn't stop me from gritting my teeth from<br>
> what I see as an annoyance.<br>
><br>
> I think that I was able to get myself across a little better. Let me<br>
> know if I was confusing still.<br>
><br>
> -Mike<br>
><br>
> On Mon, Mar 23, 2009 at 9:43 AM, Loïc Martin <<a href="mailto:loic.martin3@gmail.com">loic.martin3@gmail.com</a>> wrote:<br>
>><br>
>> Mike Jones wrote:<br>
>>><br>
>>> Is there just no way for a package maintaner to not have extra work<br>
>>> piled on their already hefty load while at the same time we allow a user of<br>
>>> Ubuntu to remove most traces of a program in a package with multiple<br>
>>> programs without having to also remove the rest of them? Is it worth doing<br>
>>> even if its possible? I think I'm in a somewhat unique position of having<br>
>>> extreme distaste whenever my system tells me I can't do something in a<br>
>>> counter intuitive way.<br>
>><br>
>> You can remove the program and keep the other ones in the package actually<br>
>> - nothing is preventing you to do so, even the system. The cleanest solution<br>
>> would be for you to repackage gnome-games (or whatever name the package is<br>
>> called) for your personal use, while excluding the programs you don't want.<br>
>><br>
>> Quite a lot of work for absolutely no gain, but could we expect Ubuntu<br>
>> developers and package maintainers to spend days doing that for us while we<br>
>> wouldn't spend the same amount of time ourselves (including the time<br>
>> googling for howtos and such)? Especially when they already have far more<br>
>> critical bugs to address (like when the programs don't even run, or when<br>
>> people can't install Ubuntu or run it on their machines ;) ).<br>
>><br>
>> But all in all, nothing is preventing you to do what you want to achieve.<br>
>><br>
>> Fact is, the way it's done now allows easy upgrades for millions of people<br>
>> who are quite please to see the selection of programs updated for each<br>
>> release, while said programs only take a few kb of space on their drives.<br>
>> And to be fair, when people are complaining they can't remove foo without<br>
>> removing bar or ubuntu-desktop, I always wonder why they point to programs<br>
>> that only takes a few kB of space while being oblivious to the hundreds of<br>
>> MB taken by fonts, translations, libraries, system utilities, drivers...<br>
>> they'd never use in a lifetime, but that are invaluable because they make<br>
>> peripherals, foreign languages documents and other things work out of the<br>
>> box in Linux.<br>
>><br>
>> For space-constrained drives, there's Damn Small Linux, and if we were<br>
>> shooting for that goal I'm not so sure you'd find so many developers and<br>
>> packagers in Ubuntu.<br>
>><br>
>> If unused programs are really an issue but you're not so tight on space to<br>
>> use DSL, the Ubuntu server install could probably address your needs better<br>
>> - just chose all the programs that you need one by one, and you'd end up<br>
>> with far less programs than you'd have just trying to get rid of individual<br>
>> programs in multi-program packages that show in the menus. Such a difference<br>
>> it wouldn't be funny.<br>
>><br>
>> Loďc<br>
<br>
</div></div>Hi Mike<br>
<br>
Cherry picking parts of a package is bad for the same reason that<br>
going in and using rm by hand is bad. The goal of the package manager<br>
is to keep your system in a sane state and allow you add, remove and<br>
update things without making it so you cant boot. But with cherry<br>
picking, the package manager has no way of knowing if you removing<br>
part of a package means that another package or another application or<br>
library within the current package will carry on working.<br>
<br>
So could synaptic automatically work out the dependencies? Well maybe<br>
for applications it can see what libraries are linked against. And<br>
maybe it can scan for files that are referenced. But i think there<br>
will always be things it cant resolve, it will always be a bit fragile<br>
etc. So humans will have to maintain the data that describes these<br>
'sub packages'.<br>
<br>
Of course you can disregard the above paragraph because deb packages<br>
already support this. You have a single source package and it can<br>
build the tarball and then there are .install files that say 'these<br>
files belong with this game, and these files belong with this game'.<br>
Each install file is just a list of files that the build process made<br>
that belong in a given package. Then you get exactly the behaviour you<br>
want, safely. But its more work for the maintainers, as already<br>
described.<br>
<br>
Does that make sense? This is not a technical limitation of the<br>
packaging format, more of a limitation of man power.<br>
<font color="#888888"><br>
John<br>
</font></blockquote></div><br>