Is it ok to have image with unresolved dependencies?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is it normal to remove some components, and ignore some dependencies errors?

I want to slim down an image, i really don't need most of the stuff there.
But every time i remove one thing, something else depends on it, and it goes
on untill i het something i may need, and my image remains 500 megs fat...
Please, give me some suggestions, point me to the right directions, readings.

Thanks in advance!
 
flamey said:
Is it normal to remove some components, and ignore some dependencies
errors?

I want to slim down an image, i really don't need most of the stuff
there. But every time i remove one thing, something else depends on
it, and it goes on untill i het something i may need, and my image
remains 500 megs fat... Please, give me some suggestions, point me to
the right directions, readings.

Thanks in advance!
Click to expand...

I was about to reply with "sure, it's ok as long as you test your image"
then I saw "500 megs". The whole "don't resolve" strategy is typically only
used when you're trying to reach a very small image (50meg neighborhood -
not 500meg). If you're at 500 megs, you probably started by trying to make
it as XP Pro-like as possible then wanted to trim down.

To keep images small - start small. Build just what your PMQ implies (and
you can trim that list as well - look up "Selector Prototype" in the
newsgroup for years of history). Then add just what you need to make the
image work for you + your app. That would be the 3rd party device drivers +
apps + OS dependencies implied by those. Then repeat with your app.
Sprinkle on whatever registry/etc. tweaks are appropriate for you and you're
done. This is much more effective than "throw in a bunch of stuff and
figure out what I didn't need". There are some builds where the later
approach is fine - but not for small images.
 
Back
Top